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

Provide config context on Circuits #5368

New Issue
Closed
opened 2025-12-29 19:27:13 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:27:13 +01:00
Owner
Copy Link

Originally created by @strobus on GitHub (Sep 14, 2021).

NetBox version

v2.11

Feature type

New functionality

Proposed functionality

Circuits have config context. Config context scope can be based on provider and/or circuit type.

Use case

Frequently there are configurations associated with circuits based on providers and circuit types. In my environment the configuration of device interfaces downstream of a circuit depends on the provider and circuit type. These configuration attributes are not related to any of the current config context scopes currently available. And they do not apply to the device as a whole, only to the connection with the circuit. We have our functionality working using custom fields, but this is cumbersome because the fields appear on all circuits.

Database changes

Add provider and circuit type scopes to config context. This could be presented in a similar manner to prefixes having association to either VLAN Groups or to Sites. It's either/or, mutually exclusive. The data model would have the superset, with the mutual exclusivity enforced at the API and UI.

External dependencies

None.

Originally created by @strobus on GitHub (Sep 14, 2021). ### NetBox version v2.11 ### Feature type New functionality ### Proposed functionality Circuits have config context. Config context scope can be based on provider and/or circuit type. ### Use case Frequently there are configurations associated with circuits based on providers and circuit types. In my environment the configuration of device interfaces downstream of a circuit depends on the provider and circuit type. These configuration attributes are not related to any of the current config context scopes currently available. And they do not apply to the device as a whole, only to the connection with the circuit. We have our functionality working using custom fields, but this is cumbersome because the fields appear on all circuits. ### Database changes Add provider and circuit type scopes to config context. This could be presented in a similar manner to prefixes having association to either VLAN Groups or to Sites. It's either/or, mutually exclusive. The data model would have the superset, with the mutual exclusivity enforced at the API and UI. ### External dependencies None.
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:27:13 +01:00
adam closed this issue 2025-12-29 19:27:13 +01:00
adam commented 2025-12-29 19:27:13 +01:00
Author
Owner
Copy Link

@strobus commented on GitHub (Sep 14, 2021):

Note: I'd be willing to work on developing this if the feature is acceptable.

@strobus commented on GitHub (Sep 14, 2021): Note: I'd be willing to work on developing this if the feature is acceptable.
adam commented 2025-12-29 19:27:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2021):

The config content model is intended specifically for devices and virtual machines, which can be configured. Circuits cannot. IMO it would not make any sense to extend this to circuits. Maybe you could elaborate on your use case? What exactly are you trying to accomplish?

@jeremystretch commented on GitHub (Oct 5, 2021): The config content model is intended specifically for devices and virtual machines, which can be configured. Circuits cannot. IMO it would not make any sense to extend this to circuits. Maybe you could elaborate on your use case? What exactly are you trying to accomplish?
adam commented 2025-12-29 19:27:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 29, 2021):

Closing due to lack of response.

@jeremystretch commented on GitHub (Oct 29, 2021): Closing due to lack of response.
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: revisions needed 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#5368
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?