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

Tags logic in Config Context #10354

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

Originally created by @xcdr on GitHub (Oct 11, 2024).

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.3

Python Version

3.10

Steps to Reproduce

  • Assign tags "foo" to Virtual Machine 1
  • Assign tags "foo" and "bar" to Virtual Machine 2
  • Create Config Context with tags "foo" and "bar"

Expected Behavior

Config Context should be applied only to Virtual Machine 2

Observed Behavior

Config Context is applied to Virtual Machine 1 and Virtual Machine 2.

Other attributes have "AND" logic, while tags have "OR" logic, tested on "self-hosted" and "demo" version.

Originally created by @xcdr on GitHub (Oct 11, 2024). ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version v4.1.3 ### Python Version 3.10 ### Steps to Reproduce - Assign tags "foo" to Virtual Machine 1 - Assign tags "foo" and "bar" to Virtual Machine 2 - Create Config Context with tags "foo" and "bar" ### Expected Behavior Config Context should be applied only to Virtual Machine 2 ### Observed Behavior Config Context is applied to Virtual Machine 1 and Virtual Machine 2. Other attributes have "AND" logic, while tags have "OR" logic, tested on "self-hosted" and "demo" version.
adam added the type: bugnetbox labels 2025-12-29 21:30:24 +01:00
adam closed this issue 2025-12-29 21:30:24 +01:00
adam commented 2025-12-29 21:30:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 22, 2024):

Config Context is applied to Virtual Machine 1 and Virtual Machine 2.

This is the correct behavior. The config context will apply to objects with any (not all) of the assigned tags.

Other attributes have "AND" logic, while tags have "OR" logic

This is not accurate: The other types of associations for a config context also apply "or" logic.

@jeremystretch commented on GitHub (Oct 22, 2024): > Config Context is applied to Virtual Machine 1 and Virtual Machine 2. This is the correct behavior. The config context will apply to objects with _any_ (not all) of the assigned tags. > Other attributes have "AND" logic, while tags have "OR" logic This is not accurate: The other types of associations for a config context also apply "or" logic.
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 netbox type: bug
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#10354
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?