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
We have v1.3.3 instance and recently planned to migrate to v2.0.7. according to docs no changes were required only we had large event log data which was dumped. after migration to v2.0.7 everything is normal and all the clients are also stable. The problem comes when i try to apply new metadata to the instance it always restarts the pod and gives a 502. In the hasura logs also no error is recorded only http-log which consists of the metadata request.
We have HASURA_GRAPHQL_ENABLED_APIS=metadata,graphql,config and HASURA_GRAPHQL_ENABLED_LOG_TYPES=startup,http-log,query-log,websocket-log,webhook-log
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
-
Hi,
We have v1.3.3 instance and recently planned to migrate to v2.0.7. according to docs no changes were required only we had large event log data which was dumped. after migration to v2.0.7 everything is normal and all the clients are also stable. The problem comes when i try to apply new metadata to the instance it always restarts the pod and gives a 502. In the hasura logs also no error is recorded only http-log which consists of the metadata request.
We have
HASURA_GRAPHQL_ENABLED_APIS=metadata,graphql,configandHASURA_GRAPHQL_ENABLED_LOG_TYPES=startup,http-log,query-log,websocket-log,webhook-logBeta Was this translation helpful? Give feedback.
All reactions