Inherit Config Context Data in Device Role Hierarchy #11066

New Issue

adam · 2025-12-29T21:39:48+01:00

adam commented

2025-12-29 21:39:48 +01:00

Originally created by @pheus on GitHub (Apr 22, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.0-beta1

Feature type

New functionality

Proposed functionality

The new Device Role hierarchy in NetBox Beta is fantastic! To make it even more powerful, I’d love the ability for child roles to automatically inherit - and optionally override - Config Context data defined on their parent roles.

When you assign Config Context data to a parent Device Role, all of its descendants automatically receive those settings.
Child roles can extend or override individual keys without redefining the entire context.

Example:

Device Role: Switch - Config Context: { "ntp": "10.0.0.1" }
└─ Device Role: Access Switch - Config Context: { "ntp": "10.0.1.1", "syslog": "10.100.1.1" }
(inherits all other keys from “Switch”)

Final Merged Config Context for “Access Switch”:

{
  "ntp": "10.0.1.1",
  "syslog": "10.100.1.1"
}

Use case

Define global NTP and DNS settings once at a high-level role (e.g. “Switch”)
Create specialized child roles (“Access Switch”, “Distribution Switch”, etc.) that tweak only what’s different
Avoid duplication and ensure consistency across large device fleets

Benefits

DRY configuration: Don’t repeat the same context in every role
Clear hierarchy: Easily see which values are inherited vs. overridden
Faster onboarding: New roles automatically pick up baseline settings

Database changes

No new database tables required - leverage the existing Config Context model

External dependencies

None.

Originally created by @pheus on GitHub (Apr 22, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.0-beta1 ### Feature type New functionality ### Proposed functionality The new Device Role hierarchy in NetBox Beta is fantastic! To make it even more powerful, I’d love the ability for child roles to automatically inherit - and optionally override - Config Context data defined on their parent roles. - When you assign Config Context data to a parent Device Role, all of its descendants automatically receive those settings. - Child roles can extend or override individual keys without redefining the entire context. **Example**: Device Role: Switch - Config Context: `{ "ntp": "10.0.0.1" }` └─ Device Role: Access Switch - Config Context: `{ "ntp": "10.0.1.1", "syslog": "10.100.1.1" }` *(inherits all other keys from “Switch”)* **Final Merged Config Context for “Access Switch”:** ```json { "ntp": "10.0.1.1", "syslog": "10.100.1.1" } ``` ### Use case - Define global NTP and DNS settings once at a high-level role (e.g. “Switch”) - Create specialized child roles (“Access Switch”, “Distribution Switch”, etc.) that tweak only what’s different - Avoid duplication and ensure consistency across large device fleets **Benefits** - **DRY configuration**: Don’t repeat the same context in every role - **Clear hierarchy**: Easily see which values are inherited vs. overridden - **Faster onboarding**: New roles automatically pick up baseline settings ### Database changes - No new database tables required - leverage the existing Config Context model ### External dependencies None.

adam added the status: accepted type: feature complexity: medium beta labels 2025-12-29 21:39:48 +01:00

adam closed this issue

2025-12-29 21:39:49 +01:00

adam commented

2025-12-29 21:39:49 +01:00

@jeremystretch commented on GitHub (Apr 24, 2025):

I'll mark this as open for work with the presumption that we can replicate existing patterns for regions and site groups. However, if anything more complex is uncovered we may have to bump it.

@jeremystretch commented on GitHub (Apr 24, 2025): I'll mark this as open for work with the presumption that we can replicate existing patterns for regions and site groups. However, if anything more complex is uncovered we may have to bump it.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#11066