Some foreign keys were being created prior to the data migration, which was causing issues since the table they were referencing was empty. The keys are now created after the data migration.
In the down migration, extra steps were added to the data migration to correctly update the remapped goal ids.
Thanks @Mythicaeda and @skovati - I will cherry pick this commit (0d8da1f65db66f8cdeb85e5c3aeb380227463a03) on top of our v2.6.0 release to create a 2.6.1 patch release.
Description
Some foreign keys were being created prior to the data migration, which was causing issues since the table they were referencing was empty. The keys are now created after the data migration.
In the down migration, extra steps were added to the data migration to correctly update the remapped goal ids.
Verification
Tested against the aerie-dev database.
Documentation
No docs update
Future work