How to upgrade using metadata.json and cli-migrations-v2 ? #8425
Replies: 5 comments 5 replies
-
I'm having the same issue when trying to upgrade from When trying to run the image without any metadata it loads properly, and the same metadata.json file is imported successfully through the UI . Can you please advise? |
Beta Was this translation helpful? Give feedback.
-
I am using cli-migrations-v3 now. From hasura-cli I use: and then I import this directory like this: `FROM graphql-engine:v2.28.1.cli-migrations-v3 RUN mkdir /hasura-metadata COPY /hasura-metadata/` |
Beta Was this translation helpful? Give feedback.
-
I mean you have to stop using metadata.json, it only works manually with the web interface. |
Beta Was this translation helpful? Give feedback.
-
Yes that is what I do too, but not using metadata.json any more.
Reference: https://hasura.io/docs/latest/migrations-metadata-seeds/auto-apply-migrations/ |
Beta Was this translation helpful? Give feedback.
-
OK, so the problem was the usage of The solution for me was:
Note: there is a stupid bug that you have to have a
|
Beta Was this translation helpful? Give feedback.
-
I am trying to upgrade from v1.3.3 to v2.5.0, in v1.3.3 I am creating an Hasura image with my metadata.json
and this is working fine.
But if I use hasura/graphql-engine:v2.5.0.cli-migrations-v2,
I get the following error when starting my container:
time="2022-04-20T17:17:35Z" level=fatal msg="error applying metadata \n{\n "path": "$.args",\n "error": "key \"tables\" not found",\n "code": "parse-failed"\n}"
Until now I was just using a single metadata.json that was exported manually from the web console, what am I missing ?
Beta Was this translation helpful? Give feedback.
All reactions