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

Interface to VRF Associations #5671

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

Originally created by @ryanmerolle on GitHub (Nov 17, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.10

Feature type

Data model extension

Proposed functionality

Enable interface to VRF mapping.

Use case

Generally NetBox should support most base functions an interface supports. One obvious function missing in the current model is the ability to map interfaces to a VRF.

I do not know we can rush in to this without first discussing if and how should IP assignment be limited be associated to an interface only if they are both in the same VRF. This constraint could be challenging to implement given the current IP model. I think at the very least the MVP would just allow interfaces to be associated to a VRF without any constraints on IP assignments.

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Nov 17, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.10 ### Feature type Data model extension ### Proposed functionality Enable interface to VRF mapping. ### Use case Generally NetBox should support most base functions an interface supports. One obvious function missing in the current model is the ability to map interfaces to a VRF. I do not know we can rush in to this without first discussing if and how should IP assignment be limited be associated to an interface only if they are both in the same VRF. This constraint could be challenging to implement given the current IP model. I think at the very least the MVP would just allow interfaces to be associated to a VRF without any constraints on IP assignments. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:31:10 +01:00
adam closed this issue 2025-12-29 19:31:10 +01:00
adam commented 2025-12-29 19:31:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2021):

I do not know we can rush in to this without first discussing if and how should IP assignment be limited be associated to an interface only if they are both in the same VRF.

We probably don't want to enforce any validation around this, especially since it would prevent users from assigning any VRF IPs to an interface until that interface has been assigned to a VRF. I also imagine some users will prefer to assign only IPs or only interfaces to VRFs. Also custom validation is an option now for users who may want to enforce this.

@jeremystretch commented on GitHub (Nov 17, 2021): > I do not know we can rush in to this without first discussing if and how should IP assignment be limited be associated to an interface only if they are both in the same VRF. We probably don't want to enforce any validation around this, especially since it would prevent users from assigning any VRF IPs to an interface until that interface has been assigned to a VRF. I also imagine some users will prefer to assign only IPs or only interfaces to VRFs. Also [custom validation](https://netbox.readthedocs.io/en/stable/customization/custom-validation/) is an option now for users who may want to enforce this.
adam commented 2025-12-29 19:31:11 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Nov 17, 2021):

I agree with your logic.

@ryanmerolle commented on GitHub (Nov 17, 2021): I agree with your logic.
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 status: accepted 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#5671
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?