Skip to main content
Version: v2.x

Hasura CLI: hasura metadata apply

Apply Hasura Metadata on a database.

Synopsis

This command applies the Hasura GraphQL Engine Metadata saved in the database. You can use it to apply Hasura Metadata from one HGE server instance to another, such as when moving between development environments.

Further reading:

hasura metadata apply [flags]

Examples

# Apply Hasura GraphQL Engine metadata present in metadata.[yaml|json] file:
hasura metadata apply

# Use with admin secret:
hasura metadata apply --admin-secret "<admin-secret>"

# Apply metadata to an instance specified by the flag:
hasura metadata apply --endpoint "<endpoint>"

# Prevent inconsistent metadata from getting applied:
hasura metadata apply --disallow-inconsistent-metadata

Options

    --disallow-inconsistent-metadata   disallow inconsistent metadata to be applied. Defaults to false
--dry-run show metadata generated from project directory without applying to server. generated metadata will be printed as JSON by default, use -o flag for other display formats
-h, --help help for apply
-o, --output string specify an output format to show applied metadata. Allowed values: json, yaml (default "json")

Options inherited from parent commands

--admin-secret string            admin secret for Hasura GraphQL Engine (env "HASURA_GRAPHQL_ADMIN_SECRET")
--certificate-authority string path to a cert file for the certificate authority (env "HASURA_GRAPHQL_CERTIFICATE_AUTHORITY")
--endpoint string http(s) endpoint for Hasura GraphQL Engine (env "HASURA_GRAPHQL_ENDPOINT")
--envfile string .env filename to load ENV vars from (default ".env")
--insecure-skip-tls-verify skip TLS verification and disable cert checking (default: false) (env "HASURA_GRAPHQL_INSECURE_SKIP_TLS_VERIFY")
--log-level string log level (DEBUG, INFO, WARN, ERROR, FATAL) (default "INFO")
--no-color do not colorize output (default: false)
--project string directory where commands are executed (default: current dir)
--skip-update-check skip automatic update check on command execution

SEE ALSO

  • hasura metadata - Manage Hasura GraphQL Engine Metadata saved in the database

Auto generated by spf13/cobra