Re-adding associations between Organization and Namespaces
What does this MR do and why?
Important: This is to be released for self-managed with Milestone 16.2
Step 2 of #412771 (closed)
Re-adding associations between Organization and Namespaces
More context
When this MR was merged, it caused an incident on GitLab.com. So to avoid the same thing happening on Self-Managed instances we introduced the first revert MR, which still keeps the schema changes on the affected environments. But we introduced a couple of fix MRs in 16.1 already that prevents this problem from happening again when we modify the namespaces
table. Now this MR brings back the original schema changes but for milestone 16.2 when self-managed instances already have the fixes deployed from upgrading to 16.1.
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.
Related to #412771 (closed)