-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple search terms when searching for IP addresses #3525
Comments
The comma syntax would diverge from the API where we use commas to designate "and" logic. I think regex would be the best solution for this, if we took it up. |
It should be possible to pass the Additionally, I'll note that the |
Marking this accepted with the understanding that it entails improving the current filter behavior to allow multiple parameters. For example, |
Is this issue for filtering multiple ipaddresses? Or more enhancement mentioned in original proposal? |
Take a look at We can do address filtering like this with a new custom lookups.
|
Fixes #3525: Filter muiltiple ipaddress terms
Environment
Proposed Functionality
It would be useful to perform a bulk attribute update on a range of IP's within a subnet. For example, adding (or removing) tag
tester-tom
to addresses10.20.102.[50-100]
. Right now the IP search is string based (#1620), so searching for10.20.102.5
will find addresses10.20.102.5,[10.20.102.50-10.20.102.59], [10.20.102.500-599]
. In this scenario, to assign hosts10.20.102.50/24-10.20.102.100/24
to Tester Tom, we have to perform five searches:10.20.102.[5,6,7,8,9]
: for each search, select all addresses matching the query -> Edit All -> Add/Remove Tags -> Save. One suggestion is to allow the range syntax that is supported on the IP bulk add UI: i.e.10.20.102.[50-100]
. Yet another suggestion, allow for multiple comma-separated search strings e.g.:10.20.102.5,10.20.102.6
.Use Case
We oftentimes designate blocks of IP addresses within a subnet for certain purposes. For example, within a given subnet we may assign fifty contiguous addresses for use by a particular developer/tester, or for exclusive use by VMs on a given host system. We plan on "assigning" the IPs using tags, as I don't see a concept of IP "ownership" within netbox (although maybe I can use the custom data feature). These designations change fairly rapidly, so the multiple/search update workflow will become very tedious.
This request seems similar to #1410 (but is different), and is somewhat related to #834
The text was updated successfully, but these errors were encountered: