Skip to content

Remove long-running transaction while deduplicating the findings

Mehmet Emin INAC requested to merge minac_395037_remove_long_running_transaction into master

What does this MR do and why?

This MR removes a problematic transaction that can keep running really long depending on how many records it updates. As we are removing the transaction, I have updated the logic to set processing error for the security scan if the previously wrapped logic fails so the users will see that there was an error.

Also, if updating the deduplicated findings logic fails, the findings of that scan will not be ingested as part of the IngestReportService so the records will not be available on the "vulnerability report" page.

Related to Long-running transaction in Security::StoreScan... (#395037 - closed).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports