Skip to content

Transition dast_scanner_profiles to loose foreign keys

Schmil Monderer requested to merge schmil-dast_scanner_profiles into master

What does this MR do and why?

As part of the security database decomposition effort, this MR transitions the dast_scanner_profiles tables to the new db.
This is the relevant issue

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.

How to set up and validate locally

Relates to

#472357 (closed)

Merge request reports