Revert "Merge branch '476672-sec-train-prov' into 'master'"
What does this MR do and why?
The linked merge request reintroduced a mistakenly removed foreign key to the security_trainings table but did not set validation to false. We are guessing that some LooseForeignKey deletion events were unprocessed at time of execution, making it's reintroduction fail during validation.
This MR reverts the migration so that we can follow the LFK introduction process advised in https://docs.gitlab.com/ee/development/database/add_foreign_key_to_existing_column.html
Revert "Merge branch '476672-sec-train-prov' into 'master'"
This reverts merge request !162258 (merged)
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.
Purpose of revert
Checklist
-
Create an issue to reinstate the merge request and assign it to the author of the reverted merge request. -
If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken masterresolution DRI. -
If the revert involves a database migration, please read through Deleting existing migrations. -
Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.
Milestone info
-
I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*"label. -
I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*"label.
Related issues and merge requests
Edited by Gregory Havenga