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

Bulk-Delete: List Dependently-Deleted Entities #9701

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

Originally created by @chadhpaine on GitHub (May 18, 2024).

NetBox version

v3.7.4

Feature type

New functionality

Proposed functionality

When performing a bulk-deletion of entities, Netbox should ask the user to confirm the deletion of both the set of entities selected explicitly for deletion as well as the set of sub-entities that would be deleted due to those sub-entities being dependent on an entity being targeted for deletion. An example of this is of a set of devices being deleted, where the devices each carry different sets of components; the bulk-deletion view should show the list of devices the user targeted (as it currently does), and well as a list of the components from those devices that will be deleted (this is the request), with a column showing which device each component is related to.

Use case

When performing atomic-deletion of entities such as devices and components, Netbox warns that sub-entities considered dependent on the entity-being-deleted will also be deleted.

image
(from https://github.com/netbox-community/netbox/issues/15665#issuecomment-2066586599)

For purposes of this feature-request, we call such sub-entities "dependently-deleted entities" because their deletion is dependent on their association to the entity targeted for deletion - removing the association between a target entity and a sub-entity before deletion of the target entity is often sufficient to retain the sub-entity.

When performing bulk-deletion of the same kinds of targets, the bulk-deletion menu shows the list of targets, but does not for-each-target show the list of dependently-deleted entities that accompany it. As a result, the deletion of the dependently-deleted entities is therefore both silent and unacknowledged; customers may be unaware that they have removed data from their instance that they may (or may not) have wanted to retain, unless they also review the changelog.

image

This use-case is not limited to the relationship between devices and their components (#14488); it also incorporates relationships between inventory-items (and templates) and other components within a single device (#15665), between interfaces and their assigned IP addresses (#6015 mentions this feature), between virtual-machines and assigned virtual-disks (not mentioned in-issue but observed at demo.netbox.dev), and at numerous other points of entity-intersection throughout the application.

This feature would bring the functionality of the bulk-deletion view to-parity with its atomic-deletion counterpart. Providing a user with a visual reminder that their intended actions may have unintended consequences is important to ensure that customers have and consider their choice of which data to retain and which to discard.

Database changes

None

External dependencies

None

Originally created by @chadhpaine on GitHub (May 18, 2024). ### NetBox version v3.7.4 ### Feature type New functionality ### Proposed functionality When performing a bulk-deletion of entities, Netbox should ask the user to confirm the deletion of both the set of entities selected explicitly for deletion as well as the set of sub-entities that would be deleted due to those sub-entities being dependent on an entity being targeted for deletion. An example of this is of a set of devices being deleted, where the devices each carry different sets of components; the bulk-deletion view should show the list of devices the user targeted (as it currently does), and well as a list of the components from those devices that will be deleted (this is the request), with a column showing which device each component is related to. ### Use case When performing atomic-deletion of entities such as devices and components, Netbox warns that sub-entities considered dependent on the entity-being-deleted will also be deleted. ![image](https://github.com/netbox-community/netbox/assets/71343685/a003f788-a01c-4af1-b9d4-d29ed415135c) (from https://github.com/netbox-community/netbox/issues/15665#issuecomment-2066586599) For purposes of this feature-request, we call such sub-entities "dependently-deleted entities" because their deletion is dependent on their association to the entity targeted for deletion - removing the association between a target entity and a sub-entity before deletion of the target entity is often sufficient to retain the sub-entity. When performing bulk-deletion of the same kinds of targets, the bulk-deletion menu shows the list of targets, but does not for-each-target show the list of dependently-deleted entities that accompany it. As a result, the deletion of the dependently-deleted entities is therefore both silent and unacknowledged; customers may be unaware that they have removed data from their instance that they may (or may not) have wanted to retain, unless they also review the changelog. ![image](https://github.com/netbox-community/netbox/assets/71343685/ba1221d6-9fe8-43ee-9a14-26f31a86c619) This use-case is not limited to the relationship between devices and their components (#14488); it also incorporates relationships between inventory-items (and templates) and other components within a single device (#15665), between interfaces and their assigned IP addresses (#6015 mentions this feature), between virtual-machines and assigned virtual-disks (not mentioned in-issue but observed at demo.netbox.dev), and at numerous other points of entity-intersection throughout the application. This feature would bring the functionality of the bulk-deletion view to-parity with its atomic-deletion counterpart. Providing a user with a visual reminder that their intended actions may have unintended consequences is important to ensure that customers have and consider their choice of which data to retain and which to discard. ### Database changes None ### External dependencies None
adam added the type: featurestatus: needs ownerpending closurecomplexity: high labels 2025-12-29 21:21:13 +01:00
adam closed this issue 2025-12-29 21:21:13 +01:00
adam commented 2025-12-29 21:21:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 20, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 20, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 21:21:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 19, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 19, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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: high pending closure status: needs owner 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#9701
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?