Skip to content
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

Add start_address and end_address filters to IPRange entity API #11110

Closed
Boris-Barboris opened this issue Dec 5, 2022 · 1 comment
Closed
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@Boris-Barboris
Copy link

NetBox version

v3.3.9

Feature type

Change to existing functionality

Proposed functionality

GET api for iprange should accept start_address and end_address filters.

Use case

In API integrations lack of this functionality causes us to make full iprange search on client-side across whole VRF. The task at hand devolves into the question "does iprange with start/end parameters already exist? If yes, alter it. If not, create", hence my feature request.

Database changes

No response

External dependencies

No response

@Boris-Barboris Boris-Barboris added the type: feature Introduction of new functionality to the application label Dec 5, 2022
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Dec 5, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2023

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.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Feb 4, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Feb 17, 2023
@jeremystretch jeremystretch self-assigned this Feb 17, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants