hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-11-13 09:17:21 +03:00
Code Issues Projects Releases Wiki Activity

docs: add note about using cli-migrations-v2 image (#4618)

Browse Source
This commit is contained in:
Rikin Kachhia 2020-04-30 15:20:32 +05:30 committed by GitHub
parent 220338d5d7
commit cecec960ed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/graphql/manual/migrations/config-v1/index.rst
View File

@ -4,7 +4,7 @@
.. _migrations_v1:
Migrations & Metadata (v1 config)
Migrations & Metadata (config v1)
=================================
.. contents:: Table of contents

8
docs/graphql/manual/migrations/upgrade-v2.rst
View File

@ -24,8 +24,8 @@ directories in the Hasura project. Metadata is managed in its separate
managed via :ref:`migration files <migration_file_format_v2>` that are now in
``SQL`` format.
Changes to exising workflows
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changes needed in existing workflows
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Due to the above mentioned changes, any workflows that involve applying migrations
have an additional step of applying metadata as well.
@ -36,7 +36,9 @@ For example,
to be followed by a ``hasura metadata apply`` command.
- if the ``cli-migrations`` Docker image is used for :ref:`auto applying migrations <auto_apply_migrations>`
at server start, now the ``/metadata`` directory will also have to be mounted
at server start, now you will have to use the ``cli-migrations-v2`` image and
the ``/metadata`` directory will also have to be mounted along with the ``migrations``
directory
Upgrade steps
-------------