starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Circuits should relate to sites #8431

New Issue
Closed
opened 2025-12-29 20:36:38 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:36:38 +01:00
Owner
Copy Link

Originally created by @travisjohnsonga on GitHub (Aug 7, 2023).

NetBox version

v3.5.3

Feature type

Change to existing functionality

Proposed functionality

Circuits should have site association with them rather than tenant.

Use case

Circuits are installed at sites more specifically than tenants.

Tenants -> Sites -> Circuits

Database changes

foreign key relationship between circuits and sites

External dependencies

none that I am aware of

Originally created by @travisjohnsonga on GitHub (Aug 7, 2023). ### NetBox version v3.5.3 ### Feature type Change to existing functionality ### Proposed functionality Circuits should have site association with them rather than tenant. ### Use case Circuits are installed at sites more specifically than tenants. Tenants -> Sites -> Circuits ### Database changes foreign key relationship between circuits and sites ### External dependencies none that I am aware of
adam added the type: feature label 2025-12-29 20:36:38 +01:00
adam closed this issue 2025-12-29 20:36:38 +01:00
adam commented 2025-12-29 20:36:39 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Aug 7, 2023):

Circuits should have site association with them rather than tenant.

I would recommend reading the docs, as it seems like you are using circuits for something they are not intended for.

https://docs.netbox.dev/en/stable/features/circuits/#circuits_1

A circuit is a physical connection between two points, which is installed and maintained by an external provider. For example, an Internet connection delivered as a fiber optic cable would be modeled as a circuit in NetBox.

https://docs.netbox.dev/en/stable/models/circuits/circuit/

A circuit represents a physical point-to-point data connection, typically used to interconnect sites across considerable distances (e.g. to deliver Internet connectivity).

Circuits gets their site associations from the A and/or Z termination. A circuit within one site would just be a cable imo. I'll close this as it really doesn't make any sense with the netbox datamodel and there really isn't enough in this FR to be actionable anyway.

Feel free to update it and ping me, and I'll have another look.

@kkthxbye-code commented on GitHub (Aug 7, 2023): > Circuits should have site association with them rather than tenant. I would recommend reading the docs, as it seems like you are using circuits for something they are not intended for. https://docs.netbox.dev/en/stable/features/circuits/#circuits_1 >A circuit is a physical connection between two points, which is installed and maintained by an external provider. For example, an Internet connection delivered as a fiber optic cable would be modeled as a circuit in NetBox. https://docs.netbox.dev/en/stable/models/circuits/circuit/ > A circuit represents a physical point-to-point data connection, typically used to interconnect sites across considerable distances (e.g. to deliver Internet connectivity). Circuits gets their site associations from the A and/or Z termination. A circuit within one site would just be a cable imo. I'll close this as it really doesn't make any sense with the netbox datamodel and there really isn't enough in this FR to be actionable anyway. Feel free to update it and ping me, and I'll have another look.
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#8431
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?