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

Expose circuit terminations in interface API serializer #1031

New Issue
Closed
opened 2025-12-29 16:28:08 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:28:08 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 14, 2017).

Issue type: Feature request

Currently, the interface API serializer includes two fields relating to connections:

  • connection: InterfaceConnection object
  • connected_interface: Peer Interface object

However, this does not communicate whether an interface is in use as a circuit termination point. This information is necessary to check whether an interface is a candidate for a new connection (see #1266).

I propose replacing the two fields above with a single connection object which will contain the relevant information for either an InterfaceConnection or a CircuitTermination, as well as a connection_type field to indicate which it is. Utilizing a single field for this information allows an API consume to simply check whether or not an interface is occupied.

Originally created by @jeremystretch on GitHub (Jun 14, 2017). ### Issue type: Feature request Currently, the interface API serializer includes two fields relating to connections: * `connection`: InterfaceConnection object * `connected_interface`: Peer Interface object However, this does not communicate whether an interface is in use as a circuit termination point. This information is necessary to check whether an interface is a candidate for a new connection (see #1266). I propose replacing the two fields above with a single `connection` object which will contain the relevant information for either an InterfaceConnection or a CircuitTermination, as well as a `connection_type` field to indicate which it is. Utilizing a single field for this information allows an API consume to simply check whether or not an interface is occupied.
adam added the type: feature label 2025-12-29 16:28:08 +01:00
adam closed this issue 2025-12-29 16:28:08 +01:00
adam commented 2025-12-29 16:28:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2017):

Implemented in 8a87d60

@jeremystretch commented on GitHub (Jul 10, 2017): Implemented in 8a87d60
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#1031
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?