starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Enable ENFORCE_GLOBAL_UNIQUE by default #8973

New Issue
Closed
opened 2025-12-29 20:43:31 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:43:31 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 15, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6.6

Feature type

Change to existing functionality

Proposed functionality

Change the default value of the ENFORCE_GLOBAL_UNIQUE configuration parameter from false to true. This will enforce unique IP addressing within the global (non-VRF) table by default.

This change would affect only deployments without any configuration already defined.

Please use a 👍 or 👎 response below to indicate your support for/opposition to this proposed change.

Use case

Enforcing unique IP space by default is more restrictive and thus safer than the current default. Obviously, the parameter can still be toggled as needed.

This change would also be consistent with the enforce_unique field on the VRF model, which defaults to True.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Dec 15, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6.6 ### Feature type Change to existing functionality ### Proposed functionality Change the default value of the [`ENFORCE_GLOBAL_UNIQUE`](https://docs.netbox.dev/en/stable/configuration/miscellaneous/#enforce_global_unique) configuration parameter from false to true. This will enforce unique IP addressing within the global (non-VRF) table by default. This change would affect only deployments without any configuration already defined. Please use a :+1: or :-1: response below to indicate your support for/opposition to this proposed change. ### Use case Enforcing unique IP space by default is more restrictive and thus safer than the current default. Obviously, the parameter can still be toggled as needed. This change would also be consistent with the `enforce_unique` field on the VRF model, which defaults to True. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:43:31 +01:00
adam closed this issue 2025-12-29 20:43:31 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8973
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?