starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Negated Config Context Rules #10808

New Issue
Closed
opened 2025-12-29 21:36:08 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:36:08 +01:00
Owner
Copy Link

Originally created by @ziggekatten on GitHub (Feb 25, 2025).

NetBox version

v4.2.4

Feature type

Change to existing functionality

Proposed functionality

We heavily use Config Context to apply things for our automation. However, there are cases (for example platforms rule that get new platforms quite regularly) where it would be beneficial to be able to negate an selection. It coul be as simple as an check box bestide the rule that changes "in" to "not in"

Use case

For example, if you have multiple Platforms (Windows 2022, Ubuntu 20.04, ESXi 7 etc etc), and you regularly get new platform (as an service provider we get new stuff almost every day) you would like to apply an config context for Antivirus Config with an role "Server" and NOT "ESXi 7"

Else you need to edit Platform rule every time we get an new Platform.

Database changes

Probably not

External dependencies

No response

Originally created by @ziggekatten on GitHub (Feb 25, 2025). ### NetBox version v4.2.4 ### Feature type Change to existing functionality ### Proposed functionality We heavily use Config Context to apply things for our automation. However, there are cases (for example platforms rule that get new platforms quite regularly) where it would be beneficial to be able to negate an selection. It coul be as simple as an check box bestide the rule that changes "in" to "not in" ### Use case For example, if you have multiple Platforms (Windows 2022, Ubuntu 20.04, ESXi 7 etc etc), and you regularly get new platform (as an service provider we get new stuff almost every day) you would like to apply an config context for Antivirus Config with an role "Server" and NOT "ESXi 7" Else you need to edit Platform rule every time we get an new Platform. ### Database changes Probably not ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:36:08 +01:00
adam closed this issue 2025-12-29 21:36:09 +01:00
adam commented 2025-12-29 21:36:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 6, 2025):

While it's not a bad idea, I'm not sure this is feasible from a performance perspective given the current implementation. The proposed implementation needs to be fleshed out a lot more for consideration. @ziggekatten could you take a look at how config contexts are currently being generated and elaborate on the specific changes you're proposing?

@jeremystretch commented on GitHub (Mar 6, 2025): While it's not a bad idea, I'm not sure this is feasible from a performance perspective given the current implementation. The proposed implementation needs to be fleshed out a lot more for consideration. @ziggekatten could you take a look at how config contexts are currently being generated and elaborate on the specific changes you're proposing?
adam commented 2025-12-29 21:36:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 14, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Mar 14, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:36:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 22, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Mar 22, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 pending closure status: revisions needed 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#10808
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?