Break up remediation ingestion
Why are we doing this work
Per discussion in !49762 (comment 935454969):
In order to ingest remediations while doing a background migration, we need to be able to split up the remediation ingestion process. By using an upsert, we can get part of the remediation in the DB quickly, so we don't have a conflict with the database migration. This has the added benefit of simplifying the ingestion service.
We will use sequential flow to create remediations for findings
- Create remediations records with UPSERT queries
- Create file attachments for the created records
- Associate the remediations with findings
Relevant links
Non-functional requirements
-
Performance: Confirm no performance hits -
Testing: Confirm all tests still work, add if needed.
Implementation plan
-
backend Use sequential flow to create remediations for findings
- Create remediations records with UPSERT queries
- Create file attachments for the created records
- Associate the remediations with findings