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

Editing termination sides of a cable #3440

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

Originally created by @Yentel on GitHub (Mar 6, 2020).

Environment

  • Python version: irrelevant
  • NetBox version: 2.7.3

Proposed Functionality

When editing a cable, you are only able to edit the cable properties (cable type, cable color, cable length). However, once you've created a cable between device A port A and device B port B, you are not able to edit these terminations.

When you want to move one side of the cable to a different port, or a different device, you have to remove and re-create the cable.

Use Case

Editing existing cables that are moved to a different port or device

Database Changes

None, front-end addition

External Dependencies

None

Originally created by @Yentel on GitHub (Mar 6, 2020). ### Environment * Python version: irrelevant * NetBox version: 2.7.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality When editing a cable, you are only able to edit the cable properties (cable type, cable color, cable length). However, once you've created a cable between device A port A and device B port B, you are not able to edit these terminations. When you want to move one side of the cable to a different port, or a different device, you have to remove and re-create the cable. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Editing existing cables that are moved to a different port or device <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None, front-end addition <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 18:29:08 +01:00
adam commented 2025-12-29 18:29:09 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Mar 6, 2020):

I don't think you're supposed to be able to modify a cable's endpoint (see https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474).

@hSaria commented on GitHub (Mar 6, 2020): I don't think you're supposed to be able to modify a cable's endpoint (see https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474).
adam commented 2025-12-29 18:29:09 +01:00
Author
Owner
Copy Link

@Yentel commented on GitHub (Mar 6, 2020):

So, you never move a cable on a switch from port 1 to port 2? ;-)

On Fri, Mar 6, 2020, 12:00 Saria Hajjar notifications@github.com wrote:

I don't think you're supposed to be able to modify a cable's endpoint (see #2994
(comment)
https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474
).

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/4319?email_source=notifications&email_token=AAVBU54HEIFISCM2TYLBHJTRGDJVNA5CNFSM4LC5SWB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOA63SQ#issuecomment-595717578,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVBU52SHUJEBCQDCC3VTU3RGDJVNANCNFSM4LC5SWBQ
.

@Yentel commented on GitHub (Mar 6, 2020): So, you never move a cable on a switch from port 1 to port 2? ;-) On Fri, Mar 6, 2020, 12:00 Saria Hajjar <notifications@github.com> wrote: > I don't think you're supposed to be able to modify a cable's endpoint (see #2994 > (comment) > <https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474> > ). > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/4319?email_source=notifications&email_token=AAVBU54HEIFISCM2TYLBHJTRGDJVNA5CNFSM4LC5SWB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOA63SQ#issuecomment-595717578>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAVBU52SHUJEBCQDCC3VTU3RGDJVNANCNFSM4LC5SWBQ> > . >
adam commented 2025-12-29 18:29:09 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Mar 6, 2020):

In the real world, you do. In NetBox (as per https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474):

the cable should be deleted and a new one created with the desired endpoints.

@hSaria commented on GitHub (Mar 6, 2020): In the real world, you do. In NetBox (as per https://github.com/netbox-community/netbox/issues/2994#issuecomment-480928474): > the cable should be deleted and a new one created with the desired endpoints.
adam commented 2025-12-29 18:29:09 +01:00
Author
Owner
Copy Link

@Yentel commented on GitHub (Mar 6, 2020):

Was just able to view the referred comment from PC. Previous reply was via mail.

However, I still stand my case that it seems like an easy fix (have not checked the logics that are going on when creating or editing a cable yet) but I don't understand why:

This was never part of the intended workflow

@Yentel commented on GitHub (Mar 6, 2020): Was just able to view the referred comment from PC. Previous reply was via mail. However, I still stand my case that it seems like an easy fix (have not checked the logics that are going on when creating or editing a cable yet) but I don't understand why: > This was never part of the intended workflow
adam commented 2025-12-29 18:29:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 6, 2020):

like an easy fix (have not checked the logics that are going on when creating or editing a cable yet) but I don't understand why

Certain checks and table updates happen on the backend that make this a not ideal workflow. It is simply easier to delete and re-create the cable.

There are a number of bugs with cables right now, we won't be adding any new functionality to cables until those have been sorted out

@DanSheps commented on GitHub (Mar 6, 2020): > like an easy fix (have not checked the logics that are going on when creating or editing a cable yet) but I don't understand why Certain checks and table updates happen on the backend that make this a not ideal workflow. It is simply easier to delete and re-create the cable. There are a number of bugs with cables right now, we won't be adding any new functionality to cables until those have been sorted out
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#3440
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?