Update ingestion and service logic to fill and use `first_pipeline_id` and `latest_pipeline_id`
Once the first_pipeline_id
and latest_pipeline_id
fields have been added to the vulnerability_occurrences
table, we need to begin tracking these values during the vulnerability ingestion process.
Additionally, we want to start updating our service and api logic to use this information rather than the records in the vulnerability_occurrence_pipelines
table to provide this information to whatever may need it.
While we want the service and api logic to be behind a feature flag so that we can safely test this new logic, we will want to fill both these new fields and continue creating vulnerability_occurrence_pipeline
records until we consider the deprecation successful so that we can switch the flag on and off without information loss.
Implementation Plan
Edited by Michael Becker