[SPIKE] Test rolling back a migration on Dev space

[exalate-issue-sync]

Context: Currently just deploying an older version of the app will not undo migrations that have occurred on the database. We’re going to want to minimize the manual steps to avoid breaking things. ← especially true if there are a number of migrations in the deploy

Tasks:

1. Run an exercise of deploying a version of the app with a migration and determine what is needed to roll it back.
2. Document results in this ticket.
3. Clean up migration on DEV
4. Create follow-up ticket to implement automated rollback solution when deploying an older version of the app and address issues that arise in the process

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1871

[exalate-issue-sync]

akhorsand commented: [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] where should results be documented? What would we expect to accomplish in the follow-up ticket (just ensuring that we can roll back without issue)?

[exalate-issue-sync]

Todd Lees commented: [~accountid:61b0b42cd5986c006a9e1c94] Results should be documented in the ticket. Currently just deploying an older version of the app will not undo migrations that have occurred on the database. We’re going to want to minimize the manual steps to avoid breaking things. ← especially true if there are a number of migrations in the deploy

I predict a follow up ticket being something like “implement automated rollback solution when deploying an older version of the app”