Skip to content

Add more dast/vulnerability loose foreign keys to pipelines

Dylan Griffith requested to merge 348272-add-more-ci_pipelines-loose-foreign-keys 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".

These loose foreign keys are the first step to removing the cross-database foreign keys between main and ci databases.

These 2 foreign keys have been determined to be safe for swapping to loose foreign keys per #348272 (closed) .

These Loose foreign keys do not require any tests yet until we actually remove the foreign key as we can't validate the behaviour if the real foreign key already does the cleanup for us and we already have a test to show that deletes to namespaces are tracked.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

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

Related to #348272 (closed)

Merge request reports