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

Remove the dedicated views and REST API endpoints for console/power/interface connections #4174

New Issue
Closed
opened 2025-12-29 18:33:38 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:33:38 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Oct 8, 2020).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

NetBox currently has dedicated view and REST API endpoints for listing console, power, and interface connections. This proposal seeks to remove these completely, and merge their functionality into the new views and endpoints dedicated to each model.

Justification

The connection lists, being necessarily decoupled somewhat from their related models, don't offer as much flexibility with regard to ordering, filtering, etc. They are also limited, for instance, in that the power connections list will not display connections from power ports to power feeds.

Attaching connection information to the individual component lists should fully replicate their existing functionality. The only caveat is the interface connections list, which applies filtering to avoid showing both directions of a connection between interfaces. However, we should be able to replicate this by adding a boolean filter to the interfaces list.

Originally created by @jeremystretch on GitHub (Oct 8, 2020). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes NetBox currently has dedicated view and REST API endpoints for listing console, power, and interface connections. This proposal seeks to remove these completely, and merge their functionality into the new views and endpoints dedicated to each model. ### Justification The connection lists, being necessarily decoupled somewhat from their related models, don't offer as much flexibility with regard to ordering, filtering, etc. They are also limited, for instance, in that the power connections list will not display connections from power ports to power feeds. Attaching connection information to the individual component lists should fully replicate their existing functionality. The only caveat is the interface connections list, which applies filtering to avoid showing both directions of a connection between interfaces. However, we should be able to replicate this by adding a boolean filter to the interfaces list.
adam added the status: acceptedtype: deprecation labels 2025-12-29 18:33:38 +01:00
adam closed this issue 2025-12-29 18:33:38 +01:00
adam commented 2025-12-29 18:33:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 14, 2020):

Blocked by #4999

@jeremystretch commented on GitHub (Oct 14, 2020): Blocked by #4999
adam commented 2025-12-29 18:33:39 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jun 3, 2021):

No objections here if views can replicate "similarish" sort of output.

@ryanmerolle commented on GitHub (Jun 3, 2021): No objections here if views can replicate "similarish" sort of output.
adam commented 2025-12-29 18:33:39 +01:00
Author
Owner
Copy Link

@minitriga commented on GitHub (Jun 7, 2021):

As long as we can get the data for console, power and interface connections via other API calls that should be fine.

@minitriga commented on GitHub (Jun 7, 2021): As long as we can get the data for console, power and interface connections via other API calls that should be fine.
adam commented 2025-12-29 18:33:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 8, 2021):

I'm going to remove the REST API endpoints for these connections since they're largely redundant, but leave the UI views in place as I can see how having them separate from the component views is convenient. Maybe we'll revisit the UI views once we have a more robust mechanism around table preferences in place (to remember/re-apply saved configurations).

@jeremystretch commented on GitHub (Jul 8, 2021): I'm going to remove the REST API endpoints for these connections since they're largely redundant, but leave the UI views in place as I can see how having them separate from the component views is convenient. Maybe we'll revisit the UI views once we have a more robust mechanism around table preferences in place (to remember/re-apply saved configurations).
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: deprecation
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#4174
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?