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

Ability to update default rack size (or add additional racks) #705

New Issue
Closed
opened 2025-12-29 16:24:57 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:24:57 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Feb 8, 2017).

We can edit most of the items within a rack, but we can't seem to edit the default size of a rack. We should probably make this something we can do :)

(adding as an issue to see if there's desire for the feature, before I work on the PR)

Originally created by @ghost on GitHub (Feb 8, 2017). We can edit most of the items within a rack, but we can't seem to edit the default size of a rack. We should probably make this something we can do :) (adding as an issue to see if there's desire for the feature, before I work on the PR)
adam closed this issue 2025-12-29 16:24:57 +01:00
adam commented 2025-12-29 16:24:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 8, 2017):

Seems excessive to me. I want to avoid adding too many configuration parameters.

@jeremystretch commented on GitHub (Feb 8, 2017): Seems excessive to me. I want to avoid adding too many configuration parameters.
adam commented 2025-12-29 16:24:57 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 8, 2017):

I guess the logic for me was that I have a few sites, some with 42, some with 45, and updating the rack field each time is annoying, but honestly it shouldn't happen more than a few dozen times in most installations that it may not actually be worth the effort. Closing unless someone else someone else pipes up in the thread.

@ghost commented on GitHub (Feb 8, 2017): I guess the logic for me was that I have a few sites, some with 42, some with 45, and updating the rack field each time is annoying, but honestly it shouldn't happen more than a few dozen times in most installations that it may not actually be worth the effort. Closing unless someone else someone else pipes up in the thread.
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#705
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?