Rolling back applied migrations
If there are any issues with changes made to the DB schema and Hasura metadata it is possible to roll back their state to a previous stable version.
config v2, see Rolling back applied migrations (config v2).
Rolling back database schema
Database schema rollbacks can be achieved via the
generated every time a schema change is made.
Here are some example scenarios:
To roll back a particular migration version:
hasura migrate apply --version 1550925483858 --type down --database-name <database-name>
To roll back the last 2 migration versions:
hasura migrate apply --down 2 --database-name <database-name>
Rollbacks will only work if there are
down migrations defined for a
e.g. The console will not generate
down migrations for SQL statements
executed from the
Rolling back Hasura metadata
As Hasura metadata is managed via snapshots of the metadata, to roll back Hasura metadata to a particular state you need the metadata snapshot at that point. This is typically achieved by marking stable checkpoints of a project in version control via commits.
git checkout <stable-feature-commit>
hasura metadata apply