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 model-specific filters for cables #8919

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

Originally created by @jeremystretch on GitHub (Dec 5, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6.6

Feature type

New functionality

Proposed functionality

Add the following query filters for cables:

  • circuittermination
  • consoleport
  • consoleserverport
  • frontport
  • interface
  • powerfeed
  • poweroutlet
  • powerport
  • rearport

These filters can be used to easily filter for cables by their terminating object(s). For example, GET /api/dcim/cables/?interface=123 will return the cable (if any) terminated to the interface with ID 123.

It should be possible to pass multiple values effecting a logical OR, to allow returning all cables attached to any of the specified terminations, e.g. GET /api/dcim/cables/?interface=123&interface=456&frontport=789.

Use case

This approach greatly simplifies filtering of cables by specific termination points. As noted in #14274, the current approach utilizing termination_type and termination_id filters is limited and error-prone.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Dec 5, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6.6 ### Feature type New functionality ### Proposed functionality Add the following query filters for cables: * `circuittermination` * `consoleport` * `consoleserverport` * `frontport` * `interface` * `powerfeed` * `poweroutlet` * `powerport` * `rearport` These filters can be used to easily filter for cables by their terminating object(s). For example, `GET /api/dcim/cables/?interface=123` will return the cable (if any) terminated to the interface with ID 123. It should be possible to pass multiple values effecting a logical OR, to allow returning all cables attached to any of the specified terminations, e.g. `GET /api/dcim/cables/?interface=123&interface=456&frontport=789`. ### Use case This approach greatly simplifies filtering of cables by specific termination points. As noted in #14274, the current approach utilizing `termination_type` and `termination_id` filters is limited and error-prone. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:42:50 +01:00
adam closed this issue 2025-12-29 20:42:50 +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#8919
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?