Duplicate Deploy Key check assumes key created in same run
Overview
Looks like the duplicate deploy key check assumes that the duplicate key was created in the same migration run. If it was created in a previous wave, it may not exist in Mongo.
Can we add a query mechanism that falls-back to checking on GitLab for the key to enable it?
Tasks
-
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
Existing UTs pass locally -
100% code coverage on new code
Weight estimation
@leopardm @pprokic @glen_miller @mlindsay @nicki_peric @bryan-may @jordan_ng
Please leave your weight estimation as a reaction to this issue (reference). The final weight will be one level higher than the majority weight.