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

Option to clone devices inside the rack when cloning a rack #9271

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

Originally created by @Zarmeck on GitHub (Feb 20, 2024).

NetBox version

3.6.5

Feature type

Data model extension

Proposed functionality

In Organization -> Rack
When editing a rack and selecting the "Clone" button, a checkbox to clone devices inside the rack should be present.

When the user press "Create", if the checkbox is checked, NetBox would clone all devices inside the rack as well.
Everything (Device names, Module Bay, Power Ports and Interfaces) would stay the same.

A validation would make sure that we won't end up with the same device name at the same site.

Use case

We manufacture racks of computers and distribute those on multiple sites. The configurations are expected to stay the same.
However, it is currently tedious to create a new rack based on an existing one using the UI.
This feature would save a lot of time.

Database changes

None

External dependencies

None

Originally created by @Zarmeck on GitHub (Feb 20, 2024). ### NetBox version 3.6.5 ### Feature type Data model extension ### Proposed functionality In Organization -> Rack When editing a rack and selecting the "Clone" button, a checkbox to clone devices inside the rack should be present. When the user press "Create", if the checkbox is checked, NetBox would clone all devices inside the rack as well. Everything (Device names, Module Bay, Power Ports and Interfaces) would stay the same. A validation would make sure that we won't end up with the same device name at the same site. ### Use case We manufacture racks of computers and distribute those on multiple sites. The configurations are expected to stay the same. However, it is currently tedious to create a new rack based on an existing one using the UI. This feature would save a lot of time. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 20:47:43 +01:00
adam closed this issue 2025-12-29 20:47:43 +01:00
adam commented 2025-12-29 20:47:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2024):

I'm afraid there are simply too many variables and unknowns for this to be feasible as a built-in function. However, you can easily write a custom script to accomplish what you need for your particular use cases and with assumption you're comfortable making on behalf of the user.

@jeremystretch commented on GitHub (Feb 20, 2024): I'm afraid there are simply too many variables and unknowns for this to be feasible as a built-in function. However, you can easily write a [custom script](https://docs.netbox.dev/en/stable/customization/custom-scripts/) to accomplish what you need for your particular use cases and with assumption you're comfortable making on behalf of the user.
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#9271
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?