Add `deprecate_vulnerability_occurrence_pipelines` feature flag
What does this MR do and why?
Context
We want to drop the vulnerability_occurrence_pipelines
table. We
have some features that currently use this table. We are migrating
those features to use new columns before dropping the table. This is
all tracked in this epic
We will need to run the existing implementation and the new implementation side-by-side for a bit to give ourselves a safe roll-back path with no data loss.
This commit
-
Adds a new
wip
feature flag calleddeprecate_vulnerability_occurrence_pipelines
-
Updates the
vulnerabilities/findings
factory to support both implementations side-by-side -
Begins using thed FF in the findings model to toggle between the two implementations
This feature flag will be transitioned to a gitlab_com_derisk
feature flag once all of the application code changes are complete and
the data backfills are complete
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
N/A
related to: #422384 (closed)
resolves: #443495 (closed)
resolves: #450945 (closed)