search

nhost / hasura-auth

Authentication for Hasura.
https://nhost.io
MIT License
376 stars 111 forks source link

upgrade Nhost .19.3 => .20.1 results in inconsistent metadata #394

Closed dohomi closed 1 year ago

dohomi commented 1 year ago

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

Screenshot 2023-05-31 at 15 02 50 Screenshot 2023-05-31 at 15 04 00
dohomi commented 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

nunopato commented 1 year ago

@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.

dohomi commented 1 year ago

yes the latest version solved it.

Kalcode commented 1 year ago

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!

dbarrosop commented 1 year ago

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)