Swap FK vulnerability_statistics to ci_pipelines for LFK
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:
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 the pipeline
object and not thelatest_pipeline_id
column directly so if the record is missing we don't show anything to users. -
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.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Douglas Barbosa Alexandre