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

Allow duplicate sites names when under different tenants #4486

New Issue
Closed
opened 2025-12-29 18:36:32 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:36:32 +01:00
Owner
Copy Link

Originally created by @quintmi on GitHub (Jan 22, 2021).

Issue Type

[X] Feature request
[] Bug report
[] Documentation

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.9

Proposed Functionality

Allow the possibility to have the same site names when they are assigned under different tenants.

Use Case

We are looking to provide the tool to our partners in order for them to populate their site information at their own responsibility. However, due to the constraint of unique site names, partner B cannot create the same site name if it is already in use by partner A or ourselves.

I agree that site names should be unique, but only within a tenant. For example, we ourselves could have a datacenter in Amsterdam, while a partner with a separate tenant provisioned would also have equipment at a site in Amsterdam, while not being able to create the site 'Amsterdam' as it's in use by us. Therefore, they always need to use a prefix to specifically identify the site.

Originally created by @quintmi on GitHub (Jan 22, 2021). ### Issue Type [X] Feature request [] Bug report [] Documentation ### Environment * Python version: 3.6.9 * NetBox version: 2.9.9 ### Proposed Functionality Allow the possibility to have the same site names when they are assigned under different tenants. ### Use Case We are looking to provide the tool to our partners in order for them to populate their site information at their own responsibility. However, due to the constraint of unique site names, partner B cannot create the same site name if it is already in use by partner A or ourselves. I agree that site names should be unique, but only within a tenant. For example, we ourselves could have a datacenter in Amsterdam, while a partner with a separate tenant provisioned would also have equipment at a site in Amsterdam, while not being able to create the site 'Amsterdam' as it's in use by us. Therefore, they always need to use a prefix to specifically identify the site.
adam added the type: featurepending closurestatus: under review labels 2025-12-29 18:36:32 +01:00
adam closed this issue 2025-12-29 18:36:33 +01:00
adam commented 2025-12-29 18:36:33 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 19, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Mar 19, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:36:34 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 14, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 14, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#4486
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?