hasura / hasura/graphql-engine

Init database migration before remote schema is running

Open
#3,729 33 comments 0 reactions 0 assignees View on GitHub
c/migrations c/server iteration t/product-platform
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

Hi, my programmers have their psql and hasura containers in their dev environment and when I need to deploy the application depending on hasura and psql to another environment I have a problem with circle dependency.

They create init migration and save it to the application repository (is it right way?) then I just create empty database and hasura engine almost without configuration and run "hasura migration apply" but our app is external graphql endpoint set in hasura with env property and our application cannot run before hasura migration init is done. So I get this error:

`FATA[0002] apply failed: [remote-schema-error] HTTP exception occurred while sending the request to https://app/graphql ($.args[2].args.remote_schemas[0])`

I got it but I do not know right way to do this steps. Can you recommend me better procedure please?

Thank you

Contributor guide

Open the contributing guide

Research direction

The report mentions psql/PostgreSQL, Hasura migrations, CircleCI, and an external /graphql endpoint, but names no repository files or tests. Start by clarifying the intended deployment sequence and reproducing the migration against an empty database while the remote schema is unavailable. Done should mean a documented, verified procedure that avoids the remote-schema error.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, postgresql
Domain
api, databases, devops
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.