Skip to content

Bulk delete findings: extension hook and optional caller context#14740

Draft
valentijnscholten wants to merge 4 commits intoDefectDojo:devfrom
valentijnscholten:feat/bulk-delete-findings-extension-point
Draft

Bulk delete findings: extension hook and optional caller context#14740
valentijnscholten wants to merge 4 commits intoDefectDojo:devfrom
valentijnscholten:feat/bulk-delete-findings-extension-point

Conversation

@valentijnscholten
Copy link
Copy Markdown
Member

@valentijnscholten valentijnscholten commented Apr 22, 2026

Summary

This change reorganizes the bulk finding delete path so downstream projects (e.g. DefectDojo Pro) can plug in a custom implementation via the existing get_custom_method pattern, without altering the default OSS behavior.

- Split internal bulk delete implementation from entry point that can
  delegate via get_custom_method(BULK_DELETE_FINDINGS_METHOD).
- Allow callers to pass optional cascade_root alongside chunk_size for
  downstream use when a custom method is configured.
@valentijnscholten valentijnscholten added this to the 2.58.0 milestone Apr 22, 2026
- Extend bulk_delete_findings entry point with optional product_id for custom methods.
- async_delete_task: resolve product once for grading and metering; pass product_id
  to bulk_delete_findings; skip perform_product_grading when deleting a Product.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants