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

Add ability to set custom Cable, Interface and Port types in configuration.py #10315

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

Originally created by @Jon-Kennedy1 on GitHub (Oct 3, 2024).

NetBox version

v4.1.1

Feature type

Change to existing functionality

Proposed functionality

Either extend the FIELD_CHOICES configuration setting (or create a new one for types specifically) in order to allow custom cable, interface and port types to be configured.

Use case

We deal with networked audio and RF equipment in our workplace, and would benefit from the ability to record all of the relevant interfaces, ports and cable types associated with these devices within netbox. This would allow us for example to use the existing cable tracing functionality of netbox to trace audio cables through audio patch panels.

Database changes

None

External dependencies

None

Originally created by @Jon-Kennedy1 on GitHub (Oct 3, 2024). ### NetBox version v4.1.1 ### Feature type Change to existing functionality ### Proposed functionality Either extend the FIELD_CHOICES configuration setting (or create a new one for types specifically) in order to allow custom cable, interface and port types to be configured. ### Use case We deal with networked audio and RF equipment in our workplace, and would benefit from the ability to record all of the relevant interfaces, ports and cable types associated with these devices within netbox. This would allow us for example to use the existing cable tracing functionality of netbox to trace audio cables through audio patch panels. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 21:29:51 +01:00
adam closed this issue 2025-12-29 21:29:51 +01:00
adam commented 2025-12-29 21:29:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 3, 2024):

Please see our FAQ for an explanation of why this is not allowed.

@jeremystretch commented on GitHub (Oct 3, 2024): Please see [our FAQ](https://github.com/netbox-community/netbox/wiki/Frequently-Asked-Questions#how-can-i-add-new-interface-types) for an explanation of why this is not allowed.
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#10315
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?