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

Inherit interface VLAN assignments from VLAN groups #7859

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

Originally created by @oneone84 on GitHub (Apr 5, 2023).

NetBox version

v3.4.3

Feature type

New functionality

Proposed functionality

I would like to have the option to inherit all vlans in a vlan group (dynamically) to an interface. As it is now, I seem to be able to select a VLAN Group for an interface, but the only functionality it seems to provide, is to filter the list of selectable tagged/untagged vlans.

If I associate an interface to a vlan group and then later on change the vlans in the group, the changes should be inherited to the interface.

I would however, be able to loop the vlans in a group, if only the interface's association with a vlan group is saved. This might be easier to implement.

Use case

It is usefull to be able to quickly modify many interfaces configured with vlan group, by changing the group instead of all those interfaces. One example could be maintining a list of vlans trunked to all hypervisors in a network.

Database changes

I would imagine that an interface would need to associate with a VLAN Group, today when selected, the group settings is lost immediately.

External dependencies

None

Originally created by @oneone84 on GitHub (Apr 5, 2023). ### NetBox version v3.4.3 ### Feature type New functionality ### Proposed functionality I would like to have the option to inherit all vlans in a vlan group (dynamically) to an interface. As it is now, I seem to be able to select a VLAN Group for an interface, but the only functionality it seems to provide, is to filter the list of selectable tagged/untagged vlans. If I associate an interface to a vlan group and then later on change the vlans in the group, the changes should be inherited to the interface. I would however, be able to loop the vlans in a group, if only the interface's association with a vlan group is saved. This might be easier to implement. ### Use case It is usefull to be able to quickly modify many interfaces configured with vlan group, by changing the group instead of all those interfaces. One example could be maintining a list of vlans trunked to all hypervisors in a network. ### Database changes I would imagine that an interface would need to associate with a VLAN Group, today when selected, the group settings is lost immediately. ### External dependencies None
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:29:06 +01:00
adam closed this issue 2025-12-29 20:29:06 +01:00
adam commented 2025-12-29 20:29:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2023):

We could associate an interface with a VLAN group, but I can't see how we'd do this in a way that doesn't break the existing direct VLAN associations. Additionally, doing so would impose a dangerous scenario where adding or removing a VLAN would result in the automatic (and potentially unexpected) manipulation of an interface's configuration.

@jeremystretch commented on GitHub (May 4, 2023): We could associate an interface with a VLAN group, but I can't see how we'd do this in a way that doesn't break the existing direct VLAN associations. Additionally, doing so would impose a dangerous scenario where adding or removing a VLAN would result in the automatic (and potentially unexpected) manipulation of an interface's configuration.
adam commented 2025-12-29 20:29:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 3, 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 (Aug 3, 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:29:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 3, 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 (Sep 3, 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 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#7859
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?