Hi Team, we are currently using v39 of spicedb and performed the migration command, we want to test out rollback to v33 version But the catch is when v33 version spins up there is health check which is expecting certain alembic version in db. Due to that pods are restarting. My question is , Is there a way to make spicedb allow this new alembic version

unfortunately no: you can't rollback a to previous versions if there is a migration in place. There is no concept of "undo migration" in SpiceDB migrations framework. If you wanted to do this manually, you'd need to know what you are doing ™️, means you need to know what the migrations did, and understand what rolling those back manually is going to look like.

Hi @vroldanbet , in documentation I have seen that there is a flag with name --datastore-allowed-migrations , can we use that flag?

yes, but I think that flag was released in a recent SpiceDB version, so it wouldn't be available in 1.33 I suspect. And it will only work if the migration was backward compatible - most SpiceDB migrations are backward compatible, but some are not.