- Hasura GraphQL engine
- Getting started
- Schema
- Queries
- Mutations
- Subscriptions
- Actions (beta)
- Remote schemas
- Event Triggers
- Authentication & Authorization
- Migrations & Metadata
- Deploying
- Hasura CLI
- Installing the Hasura CLI
- Configuration reference
- hasura
- hasura actions
- hasura actions codegen
- hasura actions create
- hasura actions use-codegen
- hasura completion
- hasura console
- hasura init
- hasura metadata
- hasura metadata apply
- hasura metadata clear
- hasura metadata diff
- hasura metadata export
- hasura metadata inconsistency
- hasura metadata inconsistency drop
- hasura metadata inconsistency list
- hasura metadata inconsistency status
- hasura metadata reload
- hasura migrate
- hasura migrate apply
- hasura migrate create
- hasura migrate squash
- hasura migrate status
- hasura plugins
- hasura plugins install
- hasura plugins list
- hasura plugins uninstall
- hasura plugins upgrade
- hasura scripts
- hasura scripts update-config-v2
- hasura update-cli
- hasura version
- Uninstalling the Hasura CLI
- API Reference
- How it works
- Troubleshooting
- Guides / Tutorials / Resources
- Vulnerability reporting / disclosure
Get instant support on our discord server
Hasura CLI: hasura scripts update-config-v2¶
Upgrade config from v1 to v2
Examples¶
# Upgrade config from v1 to v2
hasura scripts update-config-v2
# Upgrade to v2 config with metadata directory set
hasura scripts update-config-v2 --metadata-dir metadata
Options¶
--admin-secret string admin secret for Hasura GraphQL engine
--endpoint string http(s) endpoint for Hasura GraphQL engine
-h, --help help for update-config-v2
--metadata-dir string (default "metadata")
Options inherited from parent commands¶
--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
Was this page helpful?
