mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 20:41:49 +03:00
94 lines
3.5 KiB
ReStructuredText
94 lines
3.5 KiB
ReStructuredText
.. _manage_hasura_metadata:
|
|
|
|
Managing Hasura Metadata
|
|
========================
|
|
|
|
.. contents:: Table of contents
|
|
:backlinks: none
|
|
:depth: 1
|
|
:local:
|
|
|
|
If your Postgres schema is already managed with a tool like knex, TypeORM,
|
|
Django/Rails Migrations, you will still need a way to export the actions you
|
|
performed on the Hasura console to apply it later on another Hasura instance.
|
|
|
|
All the actions performed on the console, like tracking tables/views/functions,
|
|
creating relationships, configuring permissions, creating event triggers and remote
|
|
schemas, etc. can be exported as a JSON file which can be version
|
|
controlled. The contents of this JSON file is called "Hasura metadata". The
|
|
metadata file can be later imported to another Hasura instance to get the same
|
|
configuration. You can also manually edit the JSON file to add more objects to
|
|
it and then use it update the instance.
|
|
|
|
Exporting Hasura metadata
|
|
-------------------------
|
|
|
|
.. rst-class:: api_tabs
|
|
.. tabs::
|
|
|
|
.. tab:: Console
|
|
|
|
1. Click on the Settings gear icon at the top right corner of the console screen.
|
|
2. In the Settings page that open, click on the ``Export Metadata`` button.
|
|
3. This will prompt a file download for ``metadata.json``. Save the file.
|
|
|
|
.. tab:: API
|
|
|
|
The export can be done via the :doc:`Metadata API
|
|
<../api-reference/schema-metadata-api/manage-metadata>` too.
|
|
Response will be a JSON object with the Hasura metadata. Here is a example
|
|
using ``curl`` to save this as a file:
|
|
|
|
.. code-block:: bash
|
|
|
|
curl -d'{"type": "export_metadata", "args": {}}' http://localhost:8080/v1/query -o metadata.json
|
|
|
|
This command will create a ``metadata.json`` file. If admin secret is set,
|
|
add ``-H 'X-Hasura-Admin-Secret: <your-admin-secret>'`` as the API is an
|
|
admin-only API.
|
|
|
|
Importing Hasura Metadata
|
|
-------------------------
|
|
|
|
The exported metadata can be imported on another instance of Hasura to replicate
|
|
the metadata. The import can be done on the same instance and it will overwrite
|
|
the existing metadata with that instance.
|
|
|
|
.. rst-class:: api_tabs
|
|
.. tabs::
|
|
|
|
.. tab:: Console
|
|
|
|
1. Click on the Settings gear icon at the top right corner of the console screen.
|
|
2. Click on ``Import Metadata`` button.
|
|
3. Choose a ``metadata.json`` file that was exported earlier.
|
|
4. A notification should appear indicating the success or error.
|
|
|
|
.. tab:: API
|
|
|
|
The exported JSON can be imported via the :doc:`Metadata API
|
|
<../api-reference/schema-metadata-api/manage-metadata>` too.
|
|
Here is a example using ``curl``:
|
|
|
|
.. code-block:: bash
|
|
|
|
curl -d'{"type":"replace_metadata", "args":'$(cat metadata.json)'}' http://localhost:8080/v1/query
|
|
|
|
This command will read ``metadata.json`` file and makes a POST request to
|
|
replace the metadata. If admin secret is set, add ``-H
|
|
'X-Hasura-Admin-Secret: <your-admin-secret>'`` as the API is an admin-only
|
|
API.
|
|
|
|
.. note::
|
|
|
|
All the dependent objects, like tables, views, functions etc. should exist on
|
|
Postgres before importing the metadata. Otherwise, it will result in an error
|
|
saying the object does not exist. So, apply the Postgres schema first, before
|
|
importing the metadata.
|
|
|
|
|
|
The ``curl`` based API calls can be easily integrated with your CI/CD workflows.
|
|
In case you need an automated way of applying/importing the metadata, take a
|
|
look at the :doc:`CLI-Migrations <auto-apply-migrations>` docker image, which
|
|
can start GraphQL Engine after automatically importing a mounted metadata file.
|