hasura / hasura/graphql-engine
Support for metadata.json in cli-migrations/v3/docker-entrypoint.sh
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
So the hasura cli-migrations/v3 script doesnt support loading metadata.json file, only yml files in a metadata directory.
This feature is quite useful because loading JSON metadata is much faster than YML files. Also running the `hasura/graphql-engine:v2.5.0.cli-migrations-v3` container wont support loading JSON metadata on start up.
There was an attempt to do this back in the old days https://github.com/hasura/graphql-engine/pull/1968
Contributor guide
Research direction
Start with cli-migrations/v3/docker-entrypoint.sh and compare its metadata loading path with the earlier pull request #1968. Verify the v3 Docker container starts successfully when given metadata.json, while preserving existing YAML-directory loading behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100