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

Prohibit multiple connections #7117

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

Originally created by @powerscooter on GitHub (Oct 18, 2022).

NetBox version

v3.3.5

Feature type

New functionality

Proposed functionality

I need a function to disallow the new "multiple connections" feature.
We automate a lot with Netbox. With the new function it is not possible to build automation in our setup. Because we need to document 1 to 1 connections.

A multiple connection of one interface to several is difficult to evaluate.
We always name the interfaces in Netbox as they are called in the system of the device.
So you can always document a 1 to 1 connection here.

Use case

To avoid errors I must be able to switch off this function. Otherwise errors can occur in the automation.

Database changes

No response

External dependencies

No response

Originally created by @powerscooter on GitHub (Oct 18, 2022). ### NetBox version v3.3.5 ### Feature type New functionality ### Proposed functionality I need a function to disallow the new "multiple connections" feature. We automate a lot with Netbox. With the new function it is not possible to build automation in our setup. Because we need to document 1 to 1 connections. A multiple connection of one interface to several is difficult to evaluate. We always name the interfaces in Netbox as they are called in the system of the device. So you can always document a 1 to 1 connection here. ### Use case To avoid errors I must be able to switch off this function. Otherwise errors can occur in the automation. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:19:25 +01:00
adam closed this issue 2025-12-29 20:19:25 +01:00
adam commented 2025-12-29 20:19:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 18, 2022):

There's nothing preventing you from continuing to model one-to-one connections; most connections are one-to-one, and that hasn't changed. Only the way in which cables are modeled has changed. If you need assistance adapting to the new API format, please consider opening a discussion.

@jeremystretch commented on GitHub (Oct 18, 2022): There's nothing preventing you from continuing to model one-to-one connections; _most_ connections are one-to-one, and that hasn't changed. Only the way in which cables are modeled has changed. If you need assistance adapting to the new API format, please consider opening a [discussion](https://github.com/netbox-community/netbox/discussions/new).
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#7117
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?