Reorder runners backfill migrations
What does this MR do and why?
We started the runners backfill via !166520 (diffs) and then started to copy over the taggings with !175578 (merged). These were added before the same required stop, so the order of the execution for the migrations was id, table_name ensuring that the runners migration is completed before the taggigns one is started.
But then we introduced !176848 (merged) which changes the order of these migrations and now we copy the taggings before the runners and since there are no runners in that table, no tagggings will be copied over.
In this MR we're switching the timestamps between these migrations so that self-managed won't loose their data.
Backports:
- Reorder runners backfill migrations - 17.9 back... (!184345 - merged)
- Reorder runners backfill migrations - 17.8 back... (!184347 - merged)
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #524402 (closed)