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 VRF name aliases (Alternative VRF names) #8079

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

Originally created by @DanSheps on GitHub (May 17, 2023).

NetBox version

3.5.0

Feature type

New functionality

Proposed functionality

This proposal would be to add VRF name aliases to the VRF model.

This would require adding a new model, VRFAlias and a M2M field on the VRF model.

Optionally, adding a M2M field on the Device model to associate the appropriate VRFAliases with the model may be desired.

Forms, Filtersets, Tables to support this new feature would also be required.

Use case

In existing deployments, when rolling out Netbox you may have VRF names that differ across the network. This is fine if the RD is being used as the identifier however in instances where the RD is not the identifier you may end up with multiple VRF names in NetBox but all effectively reference the same VRF.

Renaming a VRF on a device is sometimes disruptive in as it requires deletion (which can take time) and recreation of the VRF.

Database changes

+ VRFAlias:
+    name

VRF
+    aliases = M2M(to=VRFAlias)

External dependencies

No response

Originally created by @DanSheps on GitHub (May 17, 2023). ### NetBox version 3.5.0 ### Feature type New functionality ### Proposed functionality This proposal would be to add VRF name aliases to the VRF model. This would require adding a new model, VRFAlias and a M2M field on the VRF model. Optionally, adding a M2M field on the Device model to associate the appropriate VRFAliases with the model may be desired. Forms, Filtersets, Tables to support this new feature would also be required. ### Use case In existing deployments, when rolling out Netbox you may have VRF names that differ across the network. This is fine if the RD is being used as the identifier however in instances where the RD is not the identifier you may end up with multiple VRF names in NetBox but all effectively reference the same VRF. Renaming a VRF on a device is sometimes disruptive in as it requires deletion (which can take time) and recreation of the VRF. ### Database changes ``` + VRFAlias: + name VRF + aliases = M2M(to=VRFAlias) ``` ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:32:03 +01:00
adam closed this issue 2025-12-29 20:32:03 +01:00
adam commented 2025-12-29 20:32:04 +01:00
Author
Owner
Copy Link

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

In existing deployments, when rolling out Netbox you may have VRF names that differ across the network.

This seems like very poor practice. Further, I don't see the point in arbitrarily associating multiple aliases with a VRF: How would you know which alias to use on a particular device? At best, this sounds like a use case satisfied by custom fields IMO.

@jeremystretch commented on GitHub (May 25, 2023): > In existing deployments, when rolling out Netbox you may have VRF names that differ across the network. This seems like very poor practice. Further, I don't see the point in arbitrarily associating multiple aliases with a VRF: How would you know which alias to use on a particular device? At best, this sounds like a use case satisfied by custom fields IMO.
adam commented 2025-12-29 20:32:04 +01:00
Author
Owner
Copy Link

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

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