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

Add assigned parameter to the ipam/ip-addresses API endpoint #8321

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

Originally created by @atownson on GitHub (Jul 11, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.5.5

Feature type

Change to existing functionality

Proposed functionality

I propose to add an assigned boolean parameter to the ipam/ip-addresses API endpoint to handle filtering IP addresses by assignments to both interfaces and FHRP groups. The assigned_to_interface parameter currently supports filtering for assignments to interfaces only.

Use case

Adding this parameter would allow users to retrieve assigned or unassigned IP addresses via the API with regard to interface and FHRP group assignments. This would help an API integration task we have in place. Currently we are getting all IP addresses and determining if the assigned_object key has a value as a workaround. This would also better align the API with the UI table for IP Addresses as it also has an Assigned column.

Database changes

None

External dependencies

None

Originally created by @atownson on GitHub (Jul 11, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.5.5 ### Feature type Change to existing functionality ### Proposed functionality I propose to add an `assigned` boolean parameter to the ipam/ip-addresses API endpoint to handle filtering IP addresses by assignments to both interfaces and FHRP groups. The `assigned_to_interface` parameter currently supports filtering for assignments to interfaces only. ### Use case Adding this parameter would allow users to retrieve assigned or unassigned IP addresses via the API with regard to interface and FHRP group assignments. This would help an API integration task we have in place. Currently we are getting all IP addresses and determining if the `assigned_object` key has a value as a workaround. This would also better align the API with the UI table for IP Addresses as it also has an `Assigned` column. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:35:19 +01:00
adam closed this issue 2025-12-29 20:35:19 +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#8321
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?