Drop `vulnerability_occurrence_pipelines`

Once the deprecate_vulnerability_occurrence_pipelines feature flag has been successfully rolled out and set to true by default, thereby signalling that GitLab has fully transitions from the use of vulnerability_occurrence_pipeline records, then we can proceed with dropping the table, saving GitLab approximately 300GIB of space.

Implementation Plan

  • database Drop vulnerability_occurrence_pipelines
Edited Aug 17, 2023 by Gregory Havenga
Assignee Loading
Time tracking Loading