hasura / hasura/graphql-engine
Feature Request: disallow applying inconsistent metadata with hasura github deploy
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
### Is your proposal related to a problem?
Hasura's [replace metadata API](https://hasura.io/docs/latest/api-reference/metadata-api/manage-metadata/#metadata-replace-metadata) has an `allow_inconsistent_metadata` flag that defaults to `false`.
It seems the CLI defaults to setting this flag to `true`, and has a `--disallow-inconsistent-metadata` flag to set it to false.
Users of github deploys may want to opt-out of applying inconsistent metadata.
The CLI is used for Github deployments, but there does not seem to be an option to opt out of applying inconsistent metadata.
### Describe the solution you'd like
Users of gitbhub deployments should be able to opt-out of applying inconsistent metadata.
### Describe alternatives you've considered
Users may use the replace metadata apli themselves.
Contributor guide
Research direction
Start with the CLI's GitHub deployment entry point and the replace metadata API usage described in the issue. Trace where the metadata consistency flag is set, then define how GitHub deployments can opt out and verify that the option reaches the API unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100