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

Add ability to bind vlan in vlan group to site #5244

New Issue
Closed
opened 2025-12-29 19:25:49 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:25:49 +01:00
Owner
Copy Link

Originally created by @kovalev94 on GitHub (Aug 30, 2021).

NetBox version

v1.2.0

Feature type

Change to existing functionality

Proposed functionality

Now if we have a vlan existing in vlan group, we can bind it to some site, even the site is in vlan group scope.
I think a little bit illogical, because vlan groups exist for organizing your vlans, and you don't want to choose between groups or sites.
We may have an ability to bind vlan to some site. If vlan is member of vlan group with specified scope, you may bind the vlan to some site in the specified scope.

Use case

Now you should choose between site binding or group binding.
With this feature vlan groups will serve as real way to organize vlans without constraints.

Database changes

No response

External dependencies

No response

Originally created by @kovalev94 on GitHub (Aug 30, 2021). ### NetBox version v1.2.0 ### Feature type Change to existing functionality ### Proposed functionality Now if we have a vlan existing in vlan group, we can bind it to some site, even the site is in vlan group scope. I think a little bit illogical, because vlan groups exist for organizing your vlans, and you don't want to choose between groups or sites. We may have an ability to bind vlan to some site. If vlan is member of vlan group with specified scope, you may bind the vlan to some site in the specified scope. ### Use case Now you should choose between site binding or group binding. With this feature vlan groups will serve as real way to organize vlans without constraints. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:25:49 +01:00
adam closed this issue 2025-12-29 19:25:50 +01:00
adam commented 2025-12-29 19:25:50 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 3, 2021):

v1.2.0

We are no longer actively developing the 1.2.x train, please upgrade to the latest 3.0.1 release.

@DanSheps commented on GitHub (Sep 3, 2021): > v1.2.0 We are no longer actively developing the 1.2.x train, please upgrade to the latest 3.0.1 release.
adam commented 2025-12-29 19:25:51 +01:00
Author
Owner
Copy Link

@kovalev94 commented on GitHub (Sep 14, 2021):

Sorry, i was wrong - my version is v2.11.12.

@kovalev94 commented on GitHub (Sep 14, 2021): Sorry, i was wrong - my version is v2.11.12.
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#5244
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?