Transition dast_sites to loose foreign keys
What does this MR do and why?
Transitions the table dast_sites
to gitlab_sec
schema
This is part of a larger initiative to decompose the tables used by Secure: &14196
FAQ: &13043
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.
Related to #472348 (closed)
Edited by Arpit Gogia