Skip to content

Swap FK vulnerability_occurrence_pipelines.pipeline_id to ci_pipelines for LFK

Douglas Barbosa Alexandre requested to merge remove-ci_pipelines_vulnerability_occurrence_pipelines_pipeline_id-fk into master

What does this MR do and why?

Per &7249 (closed)

As part of our CI "decomposition" efforts we need to remove all foreign keys that are cross-database (ie. between the planned main and ci databases). We are going to replace them all with "loose foreign keys".

Related: #348272 (closed)

Validations

  • Best team to review (check off when reviewed): groupthreat insights devopssecure
  • No way for user to access once parent is deleted. Please explain: We are using this information to show "when the vulnerability has been introduced" and "where is the vulnerability located at". In both cases, we are working with the pipeline objects so if the column is set but the record is not found, we are handling those cases.
  • Possible to access once parent deleted but low user impact. Please explain:
  • Possible Sidekiq workers that may load directly and possibly lead to exceptions. Please explain:
  • Possible user impact to be evaluated or mitigated. Please explain:

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Douglas Barbosa Alexandre

Merge request reports