Closed dohomi closed 1 year ago
Its actually way worse. The entire refresh_tokens table disappears in the result of trying to solve the migration - afterwards the whole auth package is not usable any longer.
Downgrading is also not possible
@dohomi what version of the CLI are you using? v1.0.2
should fix this issue. Please upgrade with nhost sw upgrade
and let us know if that solves it.
yes the latest version solved it.
I am not using the nhost, I am using the auth repo for my own self-hosted hasura. I getting the same issue upgrading the repo. What is the CLI doing to fix this that I can do on my side? @nunopato , thanks!
hasura-auth updates the metadata itself, the CLI simply downloads it and places it in the right place so it is included in the next deployment (which is specific to Nhost cloud so not relevant if you aren't using it)
After upgrade .20.1 the Nhost Hasura results in inconsisten metadata. Should
nhost up
not handle the migration automatically?What are the user steps to fix the inconsistency? basically the whole table of
refresh-tokens
does not load any longer