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

Allow VLAN to be assigned to both VLAN Group and Site simultaneously #8215

New Issue
Closed
opened 2025-12-29 20:33:55 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:33:55 +01:00
Owner
Copy Link

Originally created by @BrunoBlanes on GitHub (Jun 20, 2023).

NetBox version

v3.5.3

Feature type

Change to existing functionality

Proposed functionality

I propose that we allow VLANs to be assigned to both Groups and Sites simultaneously if, and only if, said site and VLAN Group share a common region hierarchy.

Another option would be to allow this double assignment if the group scope be None, which isn't currently allowed either.

Right now, the workaround is to set the group's scope to be the same of the site, assign the VLAN to both VLAN Group and Site, then go back to said group and change the scope to whatever it used to be.

Use case

There's a use case for a single VLAN to be part of a VLAN Group and of a Site, for example:

We have a transport with one of our partners through a network exchange location in our area, for organizational purposes there's a VLAN Group for exchange VLANs, a set range for that purpose, however, for our day-to-day service, exchange VLANs are a rare occurrence, and so this group is scoped to a large geographical Region.
The exchange location though is a site, located within this larger geografical region, but still a site. Since this VLAN is configured and used in this site, and is also part of the VLAN Group range, it should be assigned to both, but that's not possible:

VLAN is assigned to group XXXX (scope: Region); cannot also assign to site YYYY.

Database changes

None that I'm aware.

External dependencies

None.

Originally created by @BrunoBlanes on GitHub (Jun 20, 2023). ### NetBox version v3.5.3 ### Feature type Change to existing functionality ### Proposed functionality I propose that we allow VLANs to be assigned to both Groups and Sites simultaneously if, and only if, said site _and_ VLAN Group share a common region hierarchy. Another option would be to allow this double assignment if the group scope be `None`, which isn't currently allowed either. Right now, the workaround is to set the group's scope to be the same of the site, assign the VLAN to both VLAN Group and Site, then go back to said group and change the scope to whatever it used to be. ### Use case There's a use case for a single VLAN to be part of a `VLAN Group` and of a `Site`, for example: We have a transport with one of our partners through a network exchange location in our area, for organizational purposes there's a `VLAN Group` for _exchange_ VLANs, a set range for that purpose, however, for our day-to-day service, exchange VLANs are a rare occurrence, and so this group is scoped to a large geographical `Region`. The exchange location though is a site, located within this larger geografical region, but still a site. Since this VLAN is configured and used in this site, and is also part of the `VLAN Group` range, it should be assigned to both, but that's not possible: `VLAN is assigned to group XXXX (scope: Region); cannot also assign to site YYYY.` ### Database changes None that I'm aware. ### External dependencies None.
adam added the type: featurepending closure labels 2025-12-29 20:33:55 +01:00
adam closed this issue 2025-12-29 20:33:56 +01:00
adam commented 2025-12-29 20:33:56 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 19, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 19, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:33:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 20, 2023):

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 (Oct 20, 2023): 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 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#8215
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?