Geo: Ensure that repository deletions are communicated to the secondary
What does this MR do?
Ensure that:
- The secondary removes the repository from disk
- The tracking database entry is removed
Why was this MR needed?
Repository deletions in a Geo primary node leave stalled repositories in a Geo secondary node.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan