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

IP Address REST API changes to accomodate FHRP Groups #6327

New Issue
Closed
opened 2025-12-29 19:39:26 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:39:26 +01:00
Owner
Copy Link

Originally created by @zmaster7 on GitHub (Apr 8, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

On the current /ipam/ip-addresses/ endpoint there is currently no GET request filter for FHRP groups. I propose either allow filtering based on both assigned_object_type and assigned_object_id. Or, add a fhrpgroup_id (group_id?) field, much like the current interface_id and vminterface_id fields.

I assume being able to filter by both assigned_object_type and assigned_object_id would be more future-proof, but I am unsure of the extra technicalities of that.

Use case

In my case, I am checking a current device configuration against NetBox to see what data already exists, and what needs to be created. I can obviously pull a larger subset of IPs and then filter after the fact, but that is not ideal.

Database changes

No response

External dependencies

No response

Originally created by @zmaster7 on GitHub (Apr 8, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality On the current /ipam/ip-addresses/ endpoint there is currently no GET request filter for FHRP groups. I propose either allow filtering based on both assigned_object_type and assigned_object_id. Or, add a fhrpgroup_id (group_id?) field, much like the current interface_id and vminterface_id fields. I assume being able to filter by both assigned_object_type and assigned_object_id would be more future-proof, but I am unsure of the extra technicalities of that. ### Use case In my case, I am checking a current device configuration against NetBox to see what data already exists, and what needs to be created. I can obviously pull a larger subset of IPs and then filter after the fact, but that is not ideal. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:39:26 +01:00
adam closed this issue 2025-12-29 19:39:26 +01:00
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#6327
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?