Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a dbdump to the migration process to allow rollbacks of schema changes #78

Open
jeremy-moffitt opened this issue Aug 6, 2021 · 1 comment

Comments

@jeremy-moffitt
Copy link
Collaborator

In order to support the ability to rollback schema changes, a copy of the database should be created prior to performing a migration. This should be automatic.

Acceptance Criteria:

  1. Migrations automatically create a dbdump prior to migration
  2. Create a set of instructions for rolling back the database using the dbdump
@jeremy-moffitt
Copy link
Collaborator Author

Note that in the short term this is a manual task and there is agreement that that is an acceptable solution for now given the infrequency of schema updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant