Backfill `initial_pipeline_id` and `latest_pipeline_id`
We need to ensure that all existing vulnerability findings have their initial_finding_pipeline
and latest_finding_pipeline
columns backfilled before dropping the vulnerability_occurrence_pipelines
table.
We will focus on backfilling the initial_pipeline_id
column first, as the latest_pipeline_id
column will be populated "naturally" by the vulnerability ingestion process.
We do not expect any circumstance under which a vulnerability_occurrence cannot have these fields fields filled in.
Implementation Plan
-
ASYNC | Create temporary indexes to support bac... (#454236 - closed) • Michael Becker • 16.11 -
SYNC | Create temporary indexes to support back... (#454239 - closed) • Michael Becker • 17.0 -
Backfill `initial_pipeline_id` column (#451180 - closed) • Michael Becker • 17.1 -
Backfill `latest_pipeline_id` column (#451181 - closed) • Michael Becker • 17.1 -
monitor progress of backfill (#462417) • Michael Becker • 17.1
Edited by Michael Becker