Handle project deletions in Geo::LogCursor

The simplest change here is to remove projects with the cursor, and this duplicates the current functionality used in system hooks.

However, until we solve gitlab-org/gitlab-ce#28283, there's a chance we could accidentally delete another project that was created with this name.

changed milestone to %9.5

changed the description

@dbalexandre Can you do an initial review here? I'm going to hold off on merging this until we know more about gitlab-org/gitlab-ce#28283.

assigned to @dbalexandre

@stanhu Thanks! The code looks good! I left some minor comments.

assigned to @stanhu

added 381 commits

• 8a6f510d...b6326824 - 379 commits from branch master
• 08aaebaa - Handle project deletions in Geo::LogCursor
• 7619ed3e - Add specs for deleting projects via Geo::LogCursor

Compare with previous version

added 155 commits

• 90521d63...c96dadf9 - 154 commits from branch master
• bc3ec5d9 - Handle project deletions in Geo::LogCursor

Compare with previous version

resolved all discussions

I'll add another MR to remove the handling of the destroy_project system hook event.

assigned to @rspeicher

unmarked as a Work In Progress

assigned to @stanhu

added 526 commits

• bc3ec5d9...5a9b6b5e - 525 commits from branch master
• b1288722 - Handle project deletions in Geo::LogCursor

Compare with previous version

resolved all discussions

assigned to @rspeicher

changed the description

@stanhu LGTM, just needs a rebase.

assigned to @stanhu

added 363 commits

• b1288722...451943c0 - 362 commits from branch master
• 25a46f98 - Handle project deletions in Geo::LogCursor

Compare with previous version

added 363 commits

• b1288722...451943c0 - 362 commits from branch master
• 25a46f98 - Handle project deletions in Geo::LogCursor

Compare with previous version

assigned to @rspeicher

resolved all discussions

approved this merge request

merged

mentioned in commit 6b2fde7e

mentioned in issue #2827 (closed)