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 connection (power / console / interface) to api #6636

New Issue
Closed
opened 2025-12-29 19:43:21 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:43:21 +01:00
Owner
Copy Link

Originally created by @powerscooter on GitHub (Jul 8, 2022).

NetBox version

v3.2.3

Feature type

New functionality

Proposed functionality

image

Hello, is it possible to make the connections, shown in the above screenshot, directly queryable via API?
So that i get a list only from the power, consoles or interface connections?

Use case

We use an application interface where we retrieve the data from Netbox via API. Since the list of cables is now very long, the query takes about 6-8 seconds.
By using filters, we were able to shorten this to less than 2 seconds.

If we could pull the lists directly one by one, there would be no need to build tedious filters here.

Database changes

No response

External dependencies

No response

Originally created by @powerscooter on GitHub (Jul 8, 2022). ### NetBox version v3.2.3 ### Feature type New functionality ### Proposed functionality <img width="250" alt="image" src="https://user-images.githubusercontent.com/18429672/177936998-c2e13920-ca60-4b17-8fee-2dab1dc0dfa8.png"> Hello, is it possible to make the connections, shown in the above screenshot, directly queryable via API? So that i get a list only from the power, consoles or interface connections? ### Use case We use an application interface where we retrieve the data from Netbox via API. Since the list of cables is now very long, the query takes about 6-8 seconds. By using filters, we were able to shorten this to less than 2 seconds. If we could pull the lists directly one by one, there would be no need to build tedious filters here. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:43:21 +01:00
adam closed this issue 2025-12-29 19:43:21 +01:00
adam commented 2025-12-29 19:43:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 7, 2022):

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 (Sep 7, 2022): 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).
adam commented 2025-12-29 19:43:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 15, 2022):

These endpoints were intentionally removed under #5223 as they are no longer needed. Additionally, cabling was overhauled in NetBox v3.3 and you may experience better performance on a newer release. If this continues to be a concern, please consider submitting a feature request to explore how the performance of existing API endpoints might be improved.

@jeremystretch commented on GitHub (Sep 15, 2022): These endpoints were intentionally removed under #5223 as they are no longer needed. Additionally, cabling was overhauled in NetBox v3.3 and you may experience better performance on a newer release. If this continues to be a concern, please consider submitting a feature request to explore how the performance of existing API endpoints might be improved.
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 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#6636
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?