starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow Virtual Circuits to be assigned to groups #10596

New Issue
Closed
opened 2025-12-29 21:33:30 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:33:30 +01:00
Owner
Copy Link

Originally created by @sleepinggenius2 on GitHub (Dec 30, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.2-beta1

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

Allow for Virtual Circuits to also be assigned to groups. I believe it's sufficient to use the existing Circuit Groups and only change the Circuit Group Assignment model to allow for selecting a Circuit or Virtual Circuit, as a given group might have a mix.

Use case

We have public cloud connectivity through both a direct connection and a backup VPN connection, so it would be nice to document the (physical) Circuit for the direct connection with a primary priority and a Virtual Circuit for the VPN with a secondary priority within the same Circuit Group. In other places, we have multiple (usually two) Virtual Circuits between locations on different VLANs and diverse paths, which we designate with different priorities. Just like we can document (physical) Circuits in this way, we should be able to do the same with Virtual Circuits.

Database changes

Either add a virtual_circuit field that is a ForeignKey to the VirtualCircuit model or change the existing circuit field to be a GenericForeignKey on the CircuitGroupAssignment model.

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Dec 30, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.2-beta1 ### Feature type Data model extension ### Triage priority N/A ### Proposed functionality Allow for Virtual Circuits to also be assigned to groups. I believe it's sufficient to use the existing Circuit Groups and only change the Circuit Group Assignment model to allow for selecting a Circuit or Virtual Circuit, as a given group might have a mix. ### Use case We have public cloud connectivity through both a direct connection and a backup VPN connection, so it would be nice to document the (physical) Circuit for the direct connection with a primary priority and a Virtual Circuit for the VPN with a secondary priority within the same Circuit Group. In other places, we have multiple (usually two) Virtual Circuits between locations on different VLANs and diverse paths, which we designate with different priorities. Just like we can document (physical) Circuits in this way, we should be able to do the same with Virtual Circuits. ### Database changes Either add a `virtual_circuit` field that is a `ForeignKey` to the `VirtualCircuit` model or change the existing `circuit` field to be a `GenericForeignKey` on the `CircuitGroupAssignment` model. ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: mediumbeta labels 2025-12-29 21:33:30 +01:00
adam closed this issue 2025-12-29 21:33:31 +01:00
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 beta complexity: medium 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#10596
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?