-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support pagination for available IPs endpoints #10777
Comments
Just 1 Up for the Issue , |
This specific use case should be covered by #9649. |
Marking this as blocked by #12180. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide. |
This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary. |
NetBox version
v3.3.6
Feature type
New functionality
Proposed functionality
I would like to specify an "offset" in the prefix available-ips endpoint query string parameters. Currently there is the capability to add "limit" to the query string parameters which defaults to 50, but "offset" is ignored.
Example:
https://demo.netbox.dev/api/ipam/prefixes/96/available-ips/?limit=1&offset=5
Use case
List out all available IP addresses for a prefix.
For our case in particular, we are using this to calculate the percent utilization for a prefix. We alert on prefixes that are over-utilized so that we can take action before running out of available IPs.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: