Adjust security report ingestion logic to set `traversal_ids` and `archived` columns for new records
Why are we doing this work
As we are introducing these new columns traversal_ids
and archived
, we want to set their values for the new records while ingesting the records.
The initial way of setting the attributes of the vulnerability_reads
records was using the database triggers but those triggers became really complex and can not perform better than an application layer logic, therefore, we need to take a different approach here and set those attributes on the application layer by a separate ingestion task.
Implementation plan
-
backend Adjust the security report ingestion logic to set the traversal_ids
andarchived
columns for the newvulnerability_reads
records
Verification steps
-
Ensure that these attributes are correctly set for the new vulnerability_reads
records during the ingestion
Edited by Mehmet Emin INAC