tobybellwood
commented
1 year ago MariaDB [infrastructure]> select * from knex_migrations;
+----+--------------------------------------------------+-------+---------------------+
| id | name | batch | migration_time |
+----+--------------------------------------------------+-------+---------------------+
| 1 | 20220908065119_initial_db.js | 1 | 2022-11-07 03:46:00 |
| 2 | 20220908065152_v2_10_validation.js | 1 | 2022-11-07 03:46:00 |
| 3 | 20221129221152_queuedstatus.js | 2 | 2022-12-16 00:05:30 |
| 4 | 20230119064648_add_admin_advanced_tasks.js | 3 | 2023-01-31 20:55:05 |
| 5 | 20230208080000_disabled_deploytargets.js | 4 | 2023-02-21 00:34:58 |
| 6 | 20230227080000_envvar_index.js | 5 | 2023-02-27 04:40:25 |
| 7 | 20230207210000_task_admin_fields.js | 6 | 2023-02-28 05:01:02 |
| 8 | 20230202013434_remove_monitoring_urls.js | 7 | 2023-02-28 06:22:21 |
| 9 | 20230329000000_add_project_build_image.js | 8 | 2023-04-24 00:43:31 |
| 10 | 20230703000000_advanced_task_default_optional.js | 9 | 2023-07-03 22:54:12 |
| 11 | 20230706000000_shared_baas_bucket.js | 10 | 2023-07-17 09:12:24 |
| 12 | 20230801000000_organizations.js | 11 | 2023-09-15 04:46:56 |
+----+--------------------------------------------------+-------+---------------------+
Post merging the organizations migration, we discovered that the naming of the migration could result in it being run out of order. This PR renames the migration to ensure it is run in sequential order