You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have a set of migrations and metadata files created via the Hasura console that I apply to my production Postgres db by running the hasura/graphql-engine:v2.4.0.cli-migrations-v3 Docker image, and I map in the /hasura-migrations and /hasura-metadata volumes.
This seems to apply the DB migrations fine, but it never seems to pick up the metadata changes, specifically ones where I add column permissions. It seems like the issue is that I'm adding a permission for a new column that is being added via a migration. And when Hasura tries to add the new permission, it still isn't aware of the column yet (perhaps it hasn't finished running the DB migration yet?). Am I doing something wrong, or is this expected behavior?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I currently have a set of migrations and metadata files created via the Hasura console that I apply to my production Postgres db by running the
hasura/graphql-engine:v2.4.0.cli-migrations-v3
Docker image, and I map in the /hasura-migrations and /hasura-metadata volumes.This seems to apply the DB migrations fine, but it never seems to pick up the metadata changes, specifically ones where I add column permissions. It seems like the issue is that I'm adding a permission for a new column that is being added via a migration. And when Hasura tries to add the new permission, it still isn't aware of the column yet (perhaps it hasn't finished running the DB migration yet?). Am I doing something wrong, or is this expected behavior?
Beta Was this translation helpful? Give feedback.
All reactions