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

Remove VLAN Name Constraint #4602

New Issue
Closed
opened 2025-12-29 18:38:08 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:38:08 +01:00
Owner
Copy Link

Originally created by @jaakub on GitHub (Feb 25, 2021).

Environment

  • Python version:
  • NetBox version:

Proposed Functionality

Allow multiple VLANs within the VLAN group to have the same name. Current constraints require a unique VLAN name within the VLAN group for each object.

Use Case

We have 100s of VLANs within the same group which do the same function, such as voice signalling, voice media, management etc. With current constraints, we need to name them in Netbox using the following naming convention <vlan-id>-<vlan-name> to achieve name uniqueness between the objects, however, in our network, they're just called <vlan-name>. I don't see the benefit of having a unique VLAN name constraint.

Database Changes

Don't think so.

External Dependencies

Again, don't think so.

Originally created by @jaakub on GitHub (Feb 25, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: * NetBox version: <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Allow multiple VLANs within the VLAN group to have the same name. Current constraints require a unique VLAN name within the VLAN group for each object. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case We have 100s of VLANs within the same group which do the same function, such as voice signalling, voice media, management etc. With current constraints, we need to name them in Netbox using the following naming convention `<vlan-id>-<vlan-name>` to achieve name uniqueness between the objects, however, in our network, they're just called `<vlan-name>`. I don't see the benefit of having a unique VLAN name constraint. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Don't think so. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Again, don't think so.
adam closed this issue 2025-12-29 18:38:08 +01:00
adam commented 2025-12-29 18:38:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 25, 2021):

@jacp9 did you mean to close this?

@jeremystretch commented on GitHub (Feb 25, 2021): @jacp9 did you mean to close this?
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
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#4602
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?