Rollback mechanism

How can we couple hasura rollback mechanism with kubernetes one ?

Example : I use the cli-image to have automated migrations. I bound sql migrations files and metadata yaml in configMaps.

Now what if a migration should be rollbacked? : Documentation talks about down.sql files but to do the rollback we have to use the hasura-cli tool.

So the kubernetes rollback won't solve the problem here.

Any suggestions ?

Start with the migration documentation covering down.sql files and the hasura-cli tool, then review how the cli-image consumes the mounted SQL migrations and metadata YAML in ConfigMaps. A complete result would define or document a reliable relationship between Kubernetes rollbacks and Hasura migration rollbacks.

Written by the indexing model from the issue text.