Geo - Make sure project does not meet selective sync rule before deleting it
requested to merge 9495-geo-make-sure-project-does-not-meet-selective-sync-constraint-before-deleting-it into master
What does this MR do?
This MR introduces the Geo::RepositoryCleanupWorker
that is responsible for project clean up. This worker is scheduled for each project when the selective sync rule changes on the Geo primary node, and make sure that the project does not satisfy the selective sync rule before deleting it.
What are the relevant issue numbers?
Closes #9495 (closed)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
EE specific content should be in the top level /ee
folder -
For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan? -
Security reports checked/validated by reviewer
Edited by Grzegorz Bizon