starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Make site facility field unique #961

New Issue
Closed
opened 2025-12-29 16:27:17 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:27:17 +01:00
Owner
Copy Link

Originally created by @InsaneSplash on GitHub (May 17, 2017).

When adding a facility ID to a Site, can it be checked for uniqueness?

Originally created by @InsaneSplash on GitHub (May 17, 2017). When adding a facility ID to a Site, can it be checked for uniqueness?
adam added the type: feature label 2025-12-29 16:27:17 +01:00
adam closed this issue 2025-12-29 16:27:17 +01:00
adam commented 2025-12-29 16:27:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2017):

This field was not originally intended to be unique. Leaving this one open for discussion.

@jeremystretch commented on GitHub (May 17, 2017): This field was not originally intended to be unique. Leaving this one open for discussion.
adam commented 2025-12-29 16:27:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 19, 2017):

I'm going to decline this feature request because IMO it's a perfectly valid use case to have two or more sites in the same facility. (Keep in mind that unlike the Rack model's facility_id field, this field is not used for the identification of an object.) For example, a company might have multiple physical presences in a datacenter and treat each as an independent site within e.g. Equinix DC6. Plus, changing a long established non-unique field to a unique field is bound to cause issues for some users.

@jeremystretch commented on GitHub (May 19, 2017): I'm going to decline this feature request because IMO it's a perfectly valid use case to have two or more sites in the same facility. (Keep in mind that unlike the Rack model's `facility_id` field, this field is not used for the identification of an object.) For example, a company might have multiple physical presences in a datacenter and treat each as an independent site within e.g. Equinix DC6. Plus, changing a long established non-unique field to a unique field is bound to cause issues for some users.
adam commented 2025-12-29 16:27:18 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (May 19, 2017):

OK, thanks for the reply.

@InsaneSplash commented on GitHub (May 19, 2017): OK, thanks for the reply.
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 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#961
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?