Make CircuitTermination a PathEndpoint #10178

Closed
opened 2025-12-29 21:27:51 +01:00 by adam · 1 comment
Owner

Originally created by @alehaa on GitHub (Sep 4, 2024).

NetBox version

v4.0.10

Feature type

Change to existing functionality

Proposed functionality

Add abstract model dcim.models.PathEndpoint to circuits.models.CircuitTermination and adjust related views accordingly.

Use case

NetBox already allows to document transit dark fiber that does not touch any device but is patched through the local network, e.g. to connect two customer sites. This means that a circuit is attached at both ends of the path, so this connection is not traced and no CablePath object is created. However, it would be very useful to know the path this connection takes, especially if it is patched across different sites.

Database changes

Using dcim.models.PathEndpoint adds an internal field to the CircuitTermination model. No explicit changes are added.

External dependencies

None

Originally created by @alehaa on GitHub (Sep 4, 2024). ### NetBox version v4.0.10 ### Feature type Change to existing functionality ### Proposed functionality Add abstract model `dcim.models.PathEndpoint` to `circuits.models.CircuitTermination` and adjust related views accordingly. ### Use case NetBox already allows to document transit dark fiber that does not touch any device but is patched through the local network, e.g. to connect two customer sites. This means that a circuit is attached at both ends of the path, so this connection is not traced and no `CablePath` object is created. However, it would be very useful to know the path this connection takes, especially if it is patched across different sites. ### Database changes Using `dcim.models.PathEndpoint` adds an internal field to the `CircuitTermination` model. No explicit changes are added. ### External dependencies None
adam added the type: featurenetbox labels 2025-12-29 21:27:51 +01:00
adam closed this issue 2025-12-29 21:27:51 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jan 10, 2025):

Unfortunately this would require fundamental changes to the way cable tracing works globally, and would result in breaking established behavior. We're going to decline this FR for now but may reconsider this in the future.

@jeremystretch commented on GitHub (Jan 10, 2025): Unfortunately this would require fundamental changes to the way cable tracing works globally, and would result in breaking established behavior. We're going to decline this FR for now but may reconsider this in the future.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10178