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

Config Context Support for Cluster Type #5637

New Issue
Closed
opened 2025-12-29 19:30:23 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:30:23 +01:00
Owner
Copy Link

Originally created by @Joshi425 on GitHub (Nov 9, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.2

Feature type

Change to existing functionality

Proposed functionality

Make it Possible to assign a Config Context to a Cluster Type. Currently only Cluster Group and Cluster are supported.
https://netbox.readthedocs.io/en/stable/models/extras/configcontext/

Use case

It makes sense to support this imo, if you run multiply cluster types and want settings to apply for a cluster type.

Database changes

No response

External dependencies

No response

Originally created by @Joshi425 on GitHub (Nov 9, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.2 ### Feature type Change to existing functionality ### Proposed functionality Make it Possible to assign a Config Context to a Cluster Type. Currently only Cluster Group and Cluster are supported. https://netbox.readthedocs.io/en/stable/models/extras/configcontext/ ### Use case It makes sense to support this imo, if you run multiply cluster types and want settings to apply for a cluster type. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:30:23 +01:00
adam closed this issue 2025-12-29 19:30:24 +01:00
adam commented 2025-12-29 19:30:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 11, 2021):

The implementation here is pretty straightforward, though I worry we may need to revisit the logic behind how context data is rendered before we extend the current model any further.

@jeremystretch commented on GitHub (Nov 11, 2021): The implementation here is pretty straightforward, though I worry we may need to revisit the logic behind how context data is rendered before we extend the current model any further.
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: 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#5637
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?