mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 18:42:30 +03:00
ca7d8b3df5
The word "reset" is little ambiguous (reset to scratch or reset to last known consistent state). metadata reset clears the all the metadata to mimic a freshly installed hasura instance. This actually invokes the clear_metadata API in the backend and hence should also be called metadata clear for perfect clarity. All references to metadata reset should be changed to metadata clear.
52 lines
1.1 KiB
ReStructuredText
52 lines
1.1 KiB
ReStructuredText
.. _hasura_metadata_clear:
|
|
|
|
Hasura CLI: hasura metadata clear
|
|
---------------------------------
|
|
|
|
Clear Hasura GraphQL Engine metadata on the database
|
|
|
|
Synopsis
|
|
~~~~~~~~
|
|
|
|
|
|
Clear Hasura GraphQL Engine metadata on the database
|
|
|
|
::
|
|
|
|
hasura metadata clear [flags]
|
|
|
|
Alias: reset
|
|
|
|
Examples
|
|
~~~~~~~~
|
|
|
|
::
|
|
|
|
# Clear all the metadata information from database:
|
|
hasura metadata clear
|
|
|
|
Options
|
|
~~~~~~~
|
|
|
|
::
|
|
|
|
--admin-secret string admin secret for Hasura GraphQL Engine
|
|
--endpoint string http(s) endpoint for Hasura GraphQL Engine
|
|
-h, --help help for clear
|
|
|
|
Options inherited from parent commands
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
::
|
|
|
|
--log-level string log level (DEBUG, INFO, WARN, ERROR, FATAL) (default "INFO")
|
|
--project string directory where commands are executed (default: current dir)
|
|
--skip-update-check Skip automatic update check on command execution
|
|
|
|
SEE ALSO
|
|
~~~~~~~~
|
|
|
|
* :ref:`hasura metadata <hasura_metadata>` - Manage Hasura GraphQL Engine metadata saved in the database
|
|
|
|
*Auto generated by spf13/cobra*
|