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.
40 lines
1.1 KiB
ReStructuredText
40 lines
1.1 KiB
ReStructuredText
.. _hasura_metadata:
|
|
|
|
Hasura CLI: hasura metadata
|
|
---------------------------
|
|
|
|
Manage Hasura GraphQL Engine metadata saved in the database
|
|
|
|
Synopsis
|
|
~~~~~~~~
|
|
|
|
|
|
Manage Hasura GraphQL Engine metadata saved in the database
|
|
|
|
Options
|
|
~~~~~~~
|
|
|
|
::
|
|
|
|
-h, --help help for metadata
|
|
|
|
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 <hasura>` - Hasura GraphQL Engine command line tool
|
|
* :ref:`hasura metadata apply <hasura_metadata_apply>` - Apply Hasura metadata on a database
|
|
* :ref:`hasura metadata clear <hasura_metadata_clear>` - Clear Hasura GraphQL Engine metadata on the database
|
|
* :ref:`hasura metadata export <hasura_metadata_export>` - Export Hasura GraphQL Engine metadata from the database
|
|
* :ref:`hasura metadata reload <hasura_metadata_reload>` - Reload Hasura GraphQL Engine metadata on the database
|
|
|
|
*Auto generated by spf13/cobra*
|