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

Ability to apply parent platform config context values to device in children platforms #11753

New Issue
Closed
opened 2025-12-29 21:49:27 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:49:27 +01:00
Owner
Copy Link

Originally created by @Alex-Ignatov on GitHub (Oct 21, 2025).

Originally assigned to: @pheus on GitHub.

NetBox version

v4.4.2

Feature type

Change to existing functionality

Proposed functionality

Config contexts can use Platforms as conditions to apply given context to a particular device. With introduction of parent field for the platforms I believe it would be beneficial for Config Contexts to apply data to device based on parent as well and not just a child.

Currently, only if device is assigned to exactly that specific platform config contexts would be applied, but we have following platform hierarchy:

  • SROS:
    • SROS-21
    • SROS-24

Config contexts defined for parent SROS will be rendered/applied for devices that have platforms SROS-21 and SROS-24.

Use case

This will remove duplication of values between children platforms, that could have been defined at parent level.

Database changes

N/A

External dependencies

N/A

Originally created by @Alex-Ignatov on GitHub (Oct 21, 2025). Originally assigned to: @pheus on GitHub. ### NetBox version v4.4.2 ### Feature type Change to existing functionality ### Proposed functionality Config contexts can use `Platforms` as conditions to apply given context to a particular device. With introduction of parent field for the platforms I believe it would be beneficial for Config Contexts to apply data to device based on parent as well and not just a child. Currently, only if device is assigned to exactly that specific platform config contexts would be applied, but we have following platform hierarchy: - SROS: - SROS-21 - SROS-24 Config contexts defined for parent SROS will be rendered/applied for devices that have platforms SROS-21 and SROS-24. ### Use case This will remove duplication of values between children platforms, that could have been defined at parent level. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurenetboxbreaking changecomplexity: low labels 2025-12-29 21:49:27 +01:00
adam closed this issue 2025-12-29 21:49:28 +01:00
adam commented 2025-12-29 21:49:28 +01:00
Author
Owner
Copy Link

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

We've flagged this as a breaking change because it will cause a change to the content of rendered config contexts in the case where a config context is already assigned to a parent platform.

@jeremystretch commented on GitHub (Oct 24, 2025): We've flagged this as a breaking change because it will cause a change to the content of rendered config contexts in the case where a config context is already assigned to a parent platform.
adam commented 2025-12-29 21:49:29 +01:00
Author
Owner
Copy Link

@Alex-Ignatov commented on GitHub (Oct 29, 2025):

Do I understand correctly that this is not possible to implement?

@Alex-Ignatov commented on GitHub (Oct 29, 2025): Do I understand correctly that this is not possible to implement?
adam commented 2025-12-29 21:49:29 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Nov 26, 2025):

Hi! I’d be interested in working on this enhancement. I realize that feature requests are typically only open for external contribution when they have the needs owner label, so I wanted to check first rather than assuming.

Would it be okay for me to take this on, and if so, could you please assign me to the issue?

Thanks a lot for your time!

@pheus commented on GitHub (Nov 26, 2025): Hi! I’d be interested in working on this enhancement. I realize that feature requests are typically only open for external contribution when they have the `needs owner` label, so I wanted to check first rather than assuming. Would it be okay for me to take this on, and if so, could you please assign me to the issue? Thanks a lot for your time!
adam commented 2025-12-29 21:49:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 26, 2025):

Sure thing @pheus!

@jeremystretch commented on GitHub (Nov 26, 2025): Sure thing @pheus!
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 breaking change complexity: low netbox 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#11753
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?