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

VRF-id / RD as input field Prefix Import #9584

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

Originally created by @oceans1908 on GitHub (May 6, 2024).

NetBox version

v3.7.6

Feature type

New functionality

Proposed functionality

With Prefix Bulk Import function, it is not possible to select a VRF when there are multiple VRF's with the same name. An extra field for RD or vrf-id (which are always unique), would allow to use the import function.

Use case

As we use multiple VRF's with the same name (we use the same VRF naming over multiple locations) we can't use the Bulk Import function.

Database changes

No response

External dependencies

No response

Originally created by @oceans1908 on GitHub (May 6, 2024). ### NetBox version v3.7.6 ### Feature type New functionality ### Proposed functionality With Prefix Bulk Import function, it is not possible to select a VRF when there are multiple VRF's with the same name. An extra field for RD or vrf-id (which are always unique), would allow to use the import function. ### Use case As we use multiple VRF's with the same name (we use the same VRF naming over multiple locations) we can't use the Bulk Import function. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:19:18 +01:00
adam closed this issue 2025-12-29 21:19:18 +01:00
adam commented 2025-12-29 21:19:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 6, 2024):

@abhi1693 why is this marked under review? The proposed functionality is already supported by simply specifying the desired accessor:

prefix,status,vrf.rd
192.0.2.0/24,active,65000:100
@jeremystretch commented on GitHub (May 6, 2024): @abhi1693 why is this marked under review? The proposed functionality is already supported by simply specifying the desired accessor: ``` prefix,status,vrf.rd 192.0.2.0/24,active,65000:100 ```
adam commented 2025-12-29 21:19:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 21, 2024):

Closing this as the proposed functionality is already possible AFAICT and there's been no further discussion.

@jeremystretch commented on GitHub (May 21, 2024): Closing this as the proposed functionality is already possible AFAICT and there's been no further discussion.
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#9584
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?