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

Provide a method to recursively delete objects #895

New Issue
Closed
opened 2025-12-29 16:26:47 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:26:47 +01:00
Owner
Copy Link

Originally created by @zevlag on GitHub (May 1, 2017).

Issue type: Feature Request

NetBox version: v2.0.0-dev: de58d0e

I attempted to delete a populated rack and it failed. I would love to be able to delete a Rack, and all associated objects. It would be awesome if I could select how far down to recurse, ie:

You are deleting this rack, would you also like to delete associated:
[ ] Devices
[ ] IP Addresses

This could also be available at other levels, such as Site or Tenant, and include other objects.

We build temporary racks and devices and move them around while in the planning stages, and this would make cleanup much easier.

Originally created by @zevlag on GitHub (May 1, 2017). ### Issue type: Feature Request NetBox version: v2.0.0-dev: de58d0e I attempted to delete a populated rack and it failed. I would love to be able to delete a Rack, and all associated objects. It would be awesome if I could select how far down to recurse, ie: You are deleting this rack, would you also like to delete associated: [ ] Devices [ ] IP Addresses This could also be available at other levels, such as Site or Tenant, and include other objects. We build temporary racks and devices and move them around while in the planning stages, and this would make cleanup much easier.
adam closed this issue 2025-12-29 16:26:47 +01:00
adam commented 2025-12-29 16:26:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2017):

I'm not sure I like this idea. Enabling recursive deletion can be extremely dangerous. I understand where you're coming from, but it opens the door for a user to mistakenly wipe out an entire site. We could mitigate the risk by explicitly listing everything to be deleted, but it's very plausible that a user will still mistakenly delete many objects in bulk. NetBox has no revision system to allow for restoration; the only avenue for recovery is restoring a database backup.

@jeremystretch commented on GitHub (May 2, 2017): I'm not sure I like this idea. Enabling recursive deletion can be _extremely_ dangerous. I understand where you're coming from, but it opens the door for a user to mistakenly wipe out an entire site. We could mitigate the risk by explicitly listing everything to be deleted, but it's very plausible that a user will still mistakenly delete many objects in bulk. NetBox has no revision system to allow for restoration; the only avenue for recovery is restoring a database backup.
adam commented 2025-12-29 16:26:48 +01:00
Author
Owner
Copy Link

@zevlag commented on GitHub (May 2, 2017):

I understand that risk, and it definitely is a concern, I'd be interested to hear from others if they think this would be useful.

@zevlag commented on GitHub (May 2, 2017): I understand that risk, and it definitely is a concern, I'd be interested to hear from others if they think this would be useful.
adam commented 2025-12-29 16:26:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 9, 2017):

Closing this out due to lack of responses and because I think it's a bad idea. I get where you're coming from, but I prefer the minor inconvenience of having to delete dependent objects (in bulk) over the increased risk of accidentally destroying data.

@jeremystretch commented on GitHub (May 9, 2017): Closing this out due to lack of responses and because I think it's a bad idea. I get where you're coming from, but I prefer the minor inconvenience of having to delete dependent objects (in bulk) over the increased risk of accidentally destroying data.
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#895
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?