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

Allow virtual circuit terminations to have custom names/identifiers #10713

New Issue
Open
opened 2025-12-29 21:35:07 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:35:07 +01:00
Owner
Copy Link

Originally created by @ebrletic on GitHub (Jan 29, 2025).

NetBox version

v4.2.2

Feature type

Data model extension

Proposed functionality

Currently when creating a virtual circuit termination it is given a default name of "{Parent Virtual Circuit Name}: Peer termination" which is the same for all terminations for that specific virtual circuit. I propose the ability the ability to specify a custom name/ID for each termination to quickly differentiate each termination.

Use case

I am currently trying to add 2 custom fields for each virtual circuit, UNI A and UNI Z which are Objects referencing virtual circuit terminations. I would like to assign IDs for each of these terminations so you can quickly see the termination ID for UNI A and UNI Z within the custom field of the virtual circuit. The current naming convention doesn't given any information on the specific termination.

Database changes

No response

External dependencies

No response

Originally created by @ebrletic on GitHub (Jan 29, 2025). ### NetBox version v4.2.2 ### Feature type Data model extension ### Proposed functionality Currently when creating a virtual circuit termination it is given a default name of "{Parent Virtual Circuit Name}: Peer termination" which is the same for all terminations for that specific virtual circuit. I propose the ability the ability to specify a custom name/ID for each termination to quickly differentiate each termination. ### Use case I am currently trying to add 2 custom fields for each virtual circuit, UNI A and UNI Z which are Objects referencing virtual circuit terminations. I would like to assign IDs for each of these terminations so you can quickly see the termination ID for UNI A and UNI Z within the custom field of the virtual circuit. The current naming convention doesn't given any information on the specific termination. ### Database changes _No response_ ### External dependencies _No response_
adam commented 2025-12-29 21:35:08 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Feb 27, 2025):

This sounds like something that could be resolved by making the __str__ representation richer rather than adding another arbitrary field in the DB.

@bctiemann commented on GitHub (Feb 27, 2025): This sounds like something that could be resolved by making the `__str__` representation richer rather than adding another arbitrary field in the DB.
adam commented 2025-12-29 21:35:08 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Feb 27, 2025):

Potentially a breaking change if there are DB changes

@bctiemann commented on GitHub (Feb 27, 2025): Potentially a breaking change if there are DB changes
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 breaking change complexity: low needs milestone netbox status: backlog 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#10713
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?