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 contexts for tags #3022

New Issue
Closed
opened 2025-12-29 18:24:51 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:24:51 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Nov 21, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.6.7

Proposed Functionality

Now that tags are objects which are visible and editable in their own right, I would like to be able to create Config Contexts on tags.

Use Case

Tags are the only generic grouping mechanism which exists in Netbox. A device can only belong to one Role, one Site, one Platform and one Tenant.

Roles are not always sufficiently fine-grained for applying configuration. You don't want to have to create a separate role for every combination of tags (e.g. Production_Database_Slave_Canary)

Database Changes

Extra column on tag: config context

External Dependencies

None

Originally created by @candlerb on GitHub (Nov 21, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.6.7 ### Proposed Functionality Now that tags are objects which are visible and editable in their own right, I would like to be able to create Config Contexts on tags. ### Use Case Tags are the only *generic* grouping mechanism which exists in Netbox. A device can only belong to one Role, one Site, one Platform and one Tenant. Roles are not always sufficiently fine-grained for applying configuration. You don't want to have to create a separate role for every combination of tags (e.g. `Production_Database_Slave_Canary`) ### Database Changes Extra column on tag: config context ### External Dependencies None
adam added the status: duplicate label 2025-12-29 18:24:51 +01:00
adam closed this issue 2025-12-29 18:24:51 +01:00
adam commented 2025-12-29 18:24:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 22, 2019):

Is this a duplicate of #3664?

@jeremystretch commented on GitHub (Nov 22, 2019): Is this a duplicate of #3664?
adam commented 2025-12-29 18:24:52 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Nov 22, 2019):

Yes, sorry I hadn't noticed that other issue.

@candlerb commented on GitHub (Nov 22, 2019): Yes, sorry I hadn't noticed that other issue.
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: duplicate
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#3022
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?