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

Extend cable schema to support assigning a site #2670

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

Originally created by @ajknv on GitHub (Jun 14, 2019).

Environment

  • Python version: 2.7.5
  • NetBox version: 2.5.13

Proposed Functionality

Would like to have a field that can be used to assign a cable to a site.

Use Case

Provides a convenient and filterable association for this type of equipment to a site, which in turn enables querying of complete inventories of equipment for a particular site. It seems fair to posit that the vast majority of cables will be entirely internal to a particular site, making this the common use case. And even for cross-site connects, it could conceivably be useful to define the site as "Intersite" or similar for quick filtering on such cables. See also https://github.com/digitalocean/netbox/issues/3259, which could help solve the problem in a more indirect way, if this RFE cannot convince of the benefit of the (simpler) schema change.

Database Changes

Add a new field for the cable type.

External Dependencies

None.

Originally created by @ajknv on GitHub (Jun 14, 2019). ### Environment * Python version: 2.7.5 * NetBox version: 2.5.13 ### Proposed Functionality Would like to have a field that can be used to assign a cable to a site. ### Use Case Provides a convenient and filterable association for this type of equipment to a site, which in turn enables querying of complete inventories of equipment for a particular site. It seems fair to posit that the vast majority of cables will be entirely internal to a particular site, making this the common use case. And even for cross-site connects, it could conceivably be useful to define the site as "Intersite" or similar for quick filtering on such cables. See also https://github.com/digitalocean/netbox/issues/3259, which could help solve the problem in a more indirect way, if this RFE cannot convince of the benefit of the (simpler) schema change. ### Database Changes Add a new field for the cable type. ### External Dependencies None.
adam closed this issue 2025-12-29 18:21:02 +01:00
adam commented 2025-12-29 18:21:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2019):

Cables are connected to device components, which in turn belong to devices that are assigned to sites. It is not necessary or logical to introduce a direct relationship between the cable and site models.

@jeremystretch commented on GitHub (Jun 14, 2019): Cables are connected to device components, which in turn belong to devices that are assigned to sites. It is not necessary or logical to introduce a direct relationship between the cable and site models.
adam commented 2025-12-29 18:21:02 +01:00
Author
Owner
Copy Link

@ajknv commented on GitHub (Jun 14, 2019):

It is not necessary or logical to introduce a direct relationship between the cable and site models.

It's not logical (or useful?) for the product to be able to answer a question of the form "This cable can be found at ___ WHERE ___?"

@ajknv commented on GitHub (Jun 14, 2019): > It is not necessary or logical to introduce a direct relationship between the cable and site models. It's not logical (or useful?) for the product to be able to answer a question of the form "This cable can be found at ___ WHERE ___?"
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
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#2670
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?