starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add start_address and end_address filters to IPRange entity API #7321

New Issue
Closed
opened 2025-12-29 20:21:45 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:21:45 +01:00
Owner
Copy Link

Originally created by @Boris-Barboris on GitHub (Dec 5, 2022).

Originally assigned to: @jeremystretch on GitHub.

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

Originally created by @Boris-Barboris on GitHub (Dec 5, 2022). Originally assigned to: @jeremystretch on GitHub. ### 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_
adam added the status: acceptedtype: feature labels 2025-12-29 20:21:45 +01:00
adam closed this issue 2025-12-29 20:21:45 +01:00
adam commented 2025-12-29 20:21:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (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[bot] commented on GitHub (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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7321
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?