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

Cluster assignment under Config Context #3144

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

Originally created by @soofff on GitHub (Jan 10, 2020).

Environment

  • Python version: 3
  • NetBox version: 2.6.11

Proposed Functionality

It is currently not possible to assign config context to cluster.
I would expect to have the possibility to assign cluster under /extras/config-contexts/1/.
Devices and virtual machines(?) would have the assigned config context.

Use Case

Devices in a cluster could have their own cluster configuration. If you have various cluster configuration you could easily assign them to the cluster which affects to all devices and maybe virtual machines.

Database Changes

I think this will need some small database changes. New cluster assignment field and references must be stored.

External Dependencies

None

Originally created by @soofff on GitHub (Jan 10, 2020). ### Environment * Python version: 3 * NetBox version: 2.6.11 ### Proposed Functionality It is currently not possible to assign config context to cluster. I would expect to have the possibility to assign cluster under `/extras/config-contexts/1/`. Devices and virtual machines(?) would have the assigned config context. ### Use Case Devices in a cluster could have their own cluster configuration. If you have various cluster configuration you could easily assign them to the cluster which affects to all devices and maybe virtual machines. ### Database Changes I think this will need some small database changes. New cluster assignment field and references must be stored. ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:26:05 +01:00
adam closed this issue 2025-12-29 18:26:06 +01:00
adam commented 2025-12-29 18:26:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 13, 2020):

I think this makes sense. Should be pretty straightforward. Need another maintainer to 👍

@jeremystretch commented on GitHub (Jan 13, 2020): I think this makes sense. Should be pretty straightforward. Need another maintainer to :+1:
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#3144
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?