Geo - Perform GeoRepositoryDestroyWorker even when repository does not exist
requested to merge 9465-geo-repositories-cleanup-worker-can-leave-orphaned-entries-in-the-tracking-database into master
What does this MR do?
This MR changes the Geo::RepositoriesCleanupWorker to perform the GeoRepositoryDestroyWorker even when the repository does not exist on disk. There is a possibility the project does not have a repository or wiki on disk, but it can have an entry in the project_registry table, e.g., when all attempts to sync the have failed. If we don't perform the destroy worker it can lead to orphaned entries in the project_registry table.
What are the relevant issue numbers?
Closes #9465 (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 /eefolder -
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