graphql-engine
graphql-engine copied to clipboard
Can/should Hasura handle rollbacks when the Github deployment feature errors out
Is your proposal related to a problem?
E.g. use-case: when applying migrations fails, the metadata is likely to be wrong/inconsistent.
Describe the solution you'd like
There are clear instructions on what to do when an issue happens (redirect to docs troubleshooting section : rollback can be done to the previous functioning state of metadata by reverting your metadata changes on your branch and then pushing to redeploy.
). However, can this integration also handle this rollback or document why it can't do so?
Yes please, rolling back the metadata to the previous functioning state upon failed migration would be essential.