DPLT-1084 Add Hasura CLI config #167
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the initial Hasura setup as config so that it can by deployed reproducibly when setting up new instances.
Typically, this config would be the source of truth for our Hasura instances, and tied to some CI pipeline to deploy it. But, this isn't feasible in our case since our config is dynamic (new indexers modify the metadata). For now, this config can be used for new instances of Hasura to ensure we have the desired initial setup.
To use this config, you'll need to have the Hasura CLI installed and
cdin to thehasura/directory. There are two main pieces to this config:metadata- defines what databases exists, which tables are tracked, and their associated permissionsmigration- defines the DB schema, and its evolutionIt's a bit weird that we have both the
hasura/andhasura-authentication-servicedirectories, I might end up moving auth underhasura/in a future PR.