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

Associate config contexts with locations #5423

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

Originally created by @Joshi425 on GitHub (Sep 24, 2021).

NetBox version

v3.0.2

Feature type

Data model extension

Proposed functionality

make config contexts work with locations and racks

Use case

we use a spine leaf setup in our dc and some maschines need to be aware of the leaf they are in. To accomplish this I wanted to create locations with the racks as children or just assign a config context to the racks in each leaf. But neither is supported yet

https://netbox.readthedocs.io/en/stable/models/extras/configcontext/

Database changes

No response

External dependencies

No response

Originally created by @Joshi425 on GitHub (Sep 24, 2021). ### NetBox version v3.0.2 ### Feature type Data model extension ### Proposed functionality make config contexts work with locations and racks ### Use case we use a spine leaf setup in our dc and some maschines need to be aware of the leaf they are in. To accomplish this I wanted to create locations with the racks as children or just assign a config context to the racks in each leaf. But neither is supported yet https://netbox.readthedocs.io/en/stable/models/extras/configcontext/ ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 19:27:47 +01:00
adam closed this issue 2025-12-29 19:27:47 +01:00
adam commented 2025-12-29 19:27:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2021):

Associating config contexts with individual racks has been discussed previously, under #4158 and #4699, and we have decided not to implement it for the reasons cited there.

@jeremystretch commented on GitHub (Sep 26, 2021): Associating config contexts with individual racks has been discussed previously, under #4158 and #4699, and we have decided not to implement it for the reasons cited there.
adam commented 2025-12-29 19:27:48 +01:00
Author
Owner
Copy Link

@Joshi425 commented on GitHub (Sep 27, 2021):

okay I see I can also make this connection with IP Ranges. Is there a way to assign a config context to IP Ranges or how can I get this information inherited down?

@Joshi425 commented on GitHub (Sep 27, 2021): okay I see I can also make this connection with IP Ranges. Is there a way to assign a config context to IP Ranges or how can I get this information inherited down?
adam commented 2025-12-29 19:27:48 +01:00
Author
Owner
Copy Link

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

@jeremystretch sorry to mention you but do you have a suggestion or point me to a way? I want to do it the right way.

@Joshi425 commented on GitHub (Oct 5, 2021): @jeremystretch sorry to mention you but do you have a suggestion or point me to a way? I want to do it the right way.
adam commented 2025-12-29 19:27:49 +01:00
Author
Owner
Copy Link

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

No, there is no relation between config contexts and IP ranges. That wouldn't make any sense. If you need help with a specific solution, please start a new discussion.

@jeremystretch commented on GitHub (Oct 5, 2021): No, there is no relation between config contexts and IP ranges. That wouldn't make any sense. If you need help with a specific solution, please start a new [discussion](https://github.com/netbox-community/netbox/discussions/new).
adam commented 2025-12-29 19:27:49 +01:00
Author
Owner
Copy Link

@Joshi425 commented on GitHub (Oct 7, 2021):

https://github.com/netbox-community/netbox/discussions/7482

@Joshi425 commented on GitHub (Oct 7, 2021): https://github.com/netbox-community/netbox/discussions/7482
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: under review 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#5423
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?