starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 06:13:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

ConfigContext doesn't evaluate parent locations #11578

New Issue
Closed
opened 2025-12-29 21:47:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:47:05 +01:00
Owner
Copy Link

Originally created by @alehaa on GitHub (Sep 5, 2025).

Originally assigned to: @pheus on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.4.0

Python Version

3.11

Steps to Reproduce

  1. Create Location A with child location B
  2. Create a Device in location B
  3. Create a ConfigContext for location A

Expected Behavior

ConfigContext is evaluated for device.

Observed Behavior

ConfigContext will only be evaluated when applied directly to location B. Since this is an organizational model that allows nesting, I would assume that ancestors would be covered in the ConfigContextQuerySet, similar to how site groups, regions, and device roles are handled. A practical use case would be assigning configuration for a specific room divided into multiple sub-locations, such as datacenter pods.

Relevant code: https://github.com/netbox-community/netbox/blob/main/netbox/extras/querysets.py#L27

Originally created by @alehaa on GitHub (Sep 5, 2025). Originally assigned to: @pheus on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.4.0 ### Python Version 3.11 ### Steps to Reproduce 1. Create `Location` A with child location B 2. Create a `Device` in location B 3. Create a `ConfigContext` for location A ### Expected Behavior `ConfigContext` is evaluated for device. ### Observed Behavior ConfigContext will only be evaluated when applied directly to location B. Since this is an organizational model that allows nesting, I would assume that ancestors would be covered in the `ConfigContextQuerySet`, similar to how site groups, regions, and device roles are handled. A practical use case would be assigning configuration for a specific room divided into multiple sub-locations, such as datacenter pods. Relevant code: https://github.com/netbox-community/netbox/blob/main/netbox/extras/querysets.py#L27
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:47:05 +01:00
adam closed this issue 2025-12-29 21:47:05 +01:00
adam commented 2025-12-29 21:47:06 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Sep 7, 2025):

I'd like to contribute this feature. Can you please assign it to me? Thanks

@pheus commented on GitHub (Sep 7, 2025): I'd like to contribute this feature. Can you please assign it to me? Thanks
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 severity: low status: accepted type: bug
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#11578
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?