Skip to content

Remove the `deprecate_vulnerability_occurrence_pipelines` FF

What does this MR do and why?

Context

We are dropping the vulnerability_occurrence_pipelines table as part of this epic

The feature flag, which re-routes code paths to alternative queries so that we are no longer reading from this table, has been globally enabled since 2024-29-08-29 and everything looks good.

The next steps for the epic are:

  1. delete all related application code from codebase
  2. add a migration to drop the table

This MR

I had opened a draft MR that removes all of the vulnerability_occurrence_pipelines application code in one go.

It was quite a large change. In an effort to make the MRs legible, I have broken the change into several MRs

This MR removes the FF and the code directly affected by its removal. This change does leave some now-dead code in place.

Further code will be removed in followup MRs

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.


resolves: #450801 (closed)
related to: #450797 (closed)
Changelog: changed
EE: true

Edited by Michael Becker

Merge request reports

Loading