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 support for a deprecated status on cables #2579

New Issue
Closed
opened 2025-12-29 18:20:06 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:20:06 +01:00
Owner
Copy Link

Originally created by @yarnocobussen on GitHub (May 3, 2019).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • NetBox version: 2.5.12

Proposed Functionality

Add a deprecated status to cables.

Use Case

Used in the workflow of cable management.

Racks provide clarity on physically adding and removing through the states reserved and deprecated. Devices have planned and decommissioning. The cable planned state can't tell you if a cable needs adding or removing.

We generate work orders for datacenter personnel by querying Netbox's API and creating tickets with the data parsed into tasks. This way we integrate our source of truth into projects and force callbacks to the Netbox system. It would be great to be able to integrate our cable management into this as well.

Database Changes

None

External Dependencies

None

Originally created by @yarnocobussen on GitHub (May 3, 2019). Originally assigned to: @jeremystretch on GitHub. ### Environment * NetBox version: 2.5.12 ### Proposed Functionality Add a deprecated status to cables. ### Use Case Used in the workflow of cable management. Racks provide clarity on physically adding and removing through the states reserved and deprecated. Devices have planned and decommissioning. The cable planned state can't tell you if a cable needs adding or removing. We generate work orders for datacenter personnel by querying Netbox's API and creating tickets with the data parsed into tasks. This way we integrate our source of truth into projects and force callbacks to the Netbox system. It would be great to be able to integrate our cable management into this as well. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:20:06 +01:00
adam closed this issue 2025-12-29 18:20:06 +01:00
adam commented 2025-12-29 18:20:07 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 3, 2019):

Just to add a little information for discussion:

Currently cable status is a boolean (0,1) value. With 0 being planned and 1 being connected.

This would obviously require a change to that. Are there any other potential status values that might ne desired?

(Keep in mind, I am not saying this is accepted or rejected, just for more informational purposes)

@DanSheps commented on GitHub (May 3, 2019): Just to add a little information for discussion: Currently cable status is a boolean (0,1) value. With 0 being planned and 1 being connected. This would obviously require a change to that. Are there any other potential status values that might ne desired? (Keep in mind, I am not saying this is accepted or rejected, just for more informational purposes)
adam commented 2025-12-29 18:20:07 +01:00
Author
Owner
Copy Link

@yarnocobussen commented on GitHub (May 3, 2019):

My apologies for missing that detail. That means accepting this request would lead to a change in functionality, instead of an addition.

We're requesting this because interfaces and cables are ineligible for custom fields. Tags seem an inappropriate alternative, but we could at least have a working solution with them if this request were to be rejected.

If the request is accepted, another desired state might be "failed", to indicate a cable needs replacing. The device model uses this as well.

@yarnocobussen commented on GitHub (May 3, 2019): My apologies for missing that detail. That means accepting this request would lead to a change in functionality, instead of an addition. We're requesting this because interfaces and cables are ineligible for custom fields. Tags seem an inappropriate alternative, but we could at least have a working solution with them if this request were to be rejected. If the request is accepted, another desired state might be "failed", to indicate a cable needs replacing. The device model uses this as well.
adam commented 2025-12-29 18:20:07 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (May 6, 2019):

Aside: Device has a recently-added "Decommissioning" status, which also captures the idea of "scheduled to be removed".

@candlerb commented on GitHub (May 6, 2019): Aside: Device has a recently-added "Decommissioning" status, which also captures the idea of "scheduled to be removed".
adam commented 2025-12-29 18:20:07 +01:00
Author
Owner
Copy Link

@Xelinor commented on GitHub (Jul 11, 2019):

Aside: Device has a recently-added "Decommissioning" status, which also captures the idea of "scheduled to be removed".

I would agree with this. It would make more sense to re-use a term used elsewhere for consistency.

Now, going against my own reccomendation above, I would also reccomend 'Inactive' as another valid choice to be included. My company often plans out patch panels for future expansion, and the wiring between the patch panels sits dark for months or even years, simply ready to be used when needed.

@Xelinor commented on GitHub (Jul 11, 2019): > Aside: Device has a recently-added "Decommissioning" status, which also captures the idea of "scheduled to be removed". I would agree with this. It would make more sense to re-use a term used elsewhere for consistency. Now, going against my own reccomendation above, I would also reccomend 'Inactive' as another valid choice to be included. My company often plans out patch panels for future expansion, and the wiring between the patch panels sits dark for months or even years, simply ready to be used when needed.
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 status: accepted 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#2579
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?