starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Bulk Import of Racks based on Rack Type #10231

New Issue
Closed
opened 2025-12-29 21:28:39 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:28:39 +01:00
Owner
Copy Link

Originally created by @jonzey0 on GitHub (Sep 12, 2024).

Originally assigned to: @pl0xym0r on GitHub.

NetBox version

v4.1.0

Feature type

Change to existing functionality

Proposed functionality

With the new feature to introduce Rack Types into NetBox. It'd be useful if we could then refer to these Rack Types when doing a Bulk Import of Racks.

Currently the Field Options do not allow for the Rack Type to be used in place of specifying the Post Width and Rack Height in RU, which means that when performing a Bulk Import or Creation of racks, they all have to be defined separately.

This both means that the Rack Types can't be used when performing a first-time database setup, and every rack needs to be defined manually. Also means that the Racks aren't associated with a Rack Type when using this method.

Use case

This would enable users to do a Bulk Import of Racks into their NetBox environment (either via API or the GUI) using the Rack Type as a template, rather than having to define the parameters manually for each record. This is a particular use case for new environments being managed by NetBox, who may require a large number of Racks to be populated as part of their initial setup.

This would also enable all the Racks created under this method to be linked to a Rack Type which would help improve the consistency of NetBox data for users.

Database changes

No response

External dependencies

No response

Originally created by @jonzey0 on GitHub (Sep 12, 2024). Originally assigned to: @pl0xym0r on GitHub. ### NetBox version v4.1.0 ### Feature type Change to existing functionality ### Proposed functionality With the new feature to introduce Rack Types into NetBox. It'd be useful if we could then refer to these Rack Types when doing a Bulk Import of Racks. Currently the Field Options do not allow for the Rack Type to be used in place of specifying the Post Width and Rack Height in RU, which means that when performing a Bulk Import or Creation of racks, they all have to be defined separately. This both means that the Rack Types can't be used when performing a first-time database setup, and every rack needs to be defined manually. Also means that the Racks aren't associated with a Rack Type when using this method. ### Use case This would enable users to do a Bulk Import of Racks into their NetBox environment (either via API or the GUI) using the Rack Type as a template, rather than having to define the parameters manually for each record. This is a particular use case for new environments being managed by NetBox, who may require a large number of Racks to be populated as part of their initial setup. This would also enable all the Racks created under this method to be linked to a Rack Type which would help improve the consistency of NetBox data for users. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:28:39 +01:00
adam closed this issue 2025-12-29 21:28:40 +01:00
adam commented 2025-12-29 21:28:40 +01:00
Author
Owner
Copy Link

@duckw commented on GitHub (Sep 12, 2024):

If this could also be extended to cover the Bulk Edit capability as well, for all the reasons listed above. Happy to log this separately if it is more appropriate.

@duckw commented on GitHub (Sep 12, 2024): If this could also be extended to cover the Bulk Edit capability as well, for all the reasons listed above. Happy to log this separately if it is more appropriate.
adam commented 2025-12-29 21:28:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 9, 2024):

@pl0xym0r could you please comment here so I can assign the FR to you for your PR?

@jeremystretch commented on GitHub (Dec 9, 2024): @pl0xym0r could you please comment here so I can assign the FR to you for your PR?
adam commented 2025-12-29 21:28:41 +01:00
Author
Owner
Copy Link

@pl0xym0r commented on GitHub (Dec 10, 2024):

fix by #18077

@pl0xym0r commented on GitHub (Dec 10, 2024): fix by #18077
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 complexity: low netbox status: accepted 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#10231
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?