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

Cables: add a field for a cable Boot / Connector Color #11252

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

Originally created by @CADbloke on GitHub (Jun 4, 2025).

NetBox version

v4.3.1

Feature type

Data model extension

Proposed functionality

Related to #17454.
A recent system I designed used only a few different colors for Cat6 cable but they used various boot colors to physically signify what network types the Cables and Interfaces belong to. I have seen heatshrink used for this purpose before too.

Use case

This is relevant for at least some users. No impact for those who ignore it. No backwards-cpmatibility issues.

Database changes

dcim\models\Cables.py#70 - add a ColorField() called connector_color . You could name it connector_boot_color but that is arguably cumbersome.

External dependencies

nil

Originally created by @CADbloke on GitHub (Jun 4, 2025). ### NetBox version v4.3.1 ### Feature type Data model extension ### Proposed functionality Related to #17454. A recent system I designed used only a few different colors for Cat6 cable but they used various boot colors to physically signify what network types the Cables and Interfaces belong to. I have seen heatshrink used for this purpose before too. ### Use case This is relevant for at least some users. No impact for those who ignore it. No backwards-cpmatibility issues. ### Database changes dcim\models\Cables.py#70 - add a `ColorField()` called `connector_color` . You could name it `connector_boot_color` but that is arguably cumbersome. ### External dependencies nil
adam added the type: feature label 2025-12-29 21:42:28 +01:00
adam closed this issue 2025-12-29 21:42:28 +01:00
adam commented 2025-12-29 21:42:29 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 5, 2025):

Thank you for submitting your idea, @CADbloke . Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.

Our view is that the best way to accomplish this is to use a custom field.

@jnovinger commented on GitHub (Jun 5, 2025): Thank you for submitting your idea, @CADbloke . Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding. Our view is that the best way to accomplish this is to [use a custom field](https://netboxlabs.com/docs/netbox/customization/custom-fields/).
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#11252
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?