You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to filter for devices or VMs which do not have a given tag applied.
Use case
When migrating parts of the infrastructure to new versions or new tooling we currently use tags to indicate that a device or a VM should get the "new stuff" which works fine. Our automation consumes the tags applied to the device/VM and does the right thing. To see which devices/VMs have to be migrated it would be nice if we could filter for devices/VMs which do not have the tag applied yet.
Database changes
None.
External dependencies
None.
The text was updated successfully, but these errors were encountered:
You can do this today on just about any endpoint with a tag filter - there's also the tag__n filter.
If you only want objects that do not contain tag-x you would add tag__n=tag-x to your query parameters. This works in both the GUI and API - although the negation filter isn't visible in the GUI, the URL query does render the proper results.
Yes, adding ?tag__n=xxx to the URL works fine for now and provides me the result I want, so I can work. Would be cool to be able to add this filter via the GUI, so if that's the intention for #7604 that would be great :)
NetBox version
v3.0.3
Feature type
Change to existing functionality
Proposed functionality
It would be nice to be able to filter for devices or VMs which do not have a given tag applied.
Use case
When migrating parts of the infrastructure to new versions or new tooling we currently use tags to indicate that a device or a VM should get the "new stuff" which works fine. Our automation consumes the tags applied to the device/VM and does the right thing. To see which devices/VMs have to be migrated it would be nice if we could filter for devices/VMs which do not have the tag applied yet.
Database changes
None.
External dependencies
None.
The text was updated successfully, but these errors were encountered: