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
Resources can be filtered for list or batch operations.
Expected behavior
Similar to the server status filter implemented in #623
Expanding filters to all resources.
These could be used to filter a resource list or to execute batch operations (#1111) on.
Activity
bannert1337 commentedon Aug 29, 2025
Some ideas that came to my mind:
--emptyfor firewalls (no rules), placement groups (no servers), networks (no resources) and load balancers (no targets)--ipv4and--ipv6for primary and floating IPs (e.g. all IPv4 or all IPv6 addresses)--only-ipv4and--only-ipv6for servers (e.g. all servers with only IPv4 or only IPv6 primary IP)--only-privateand--only-publicfor servers (e.g. all servers with only public or only private interfaces)--type <type>for servers (e.g. all servers of specific type)--location <location>for servers, primary and floating IPs, load balancers (e.g. all resources of a specific location)--network-zone <network-zone>for networks, servers (e.g. all networks or server in a specific network zone)--datacenter <datacenter>(e.g. all resources of a specific datacenter)--state <state>for firewalls, primary and floating IPs, volumes (e.g. all attached or detached)--architecture <architecture>for servers (e.g. all x86-based or all ARM-based servers)bannert1337 commentedon Aug 29, 2025
There are many use cases for these generic filters, especially with batch operations.
github-actions commentedon Nov 28, 2025
This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.