From 449a3174ad31e75d4e3ea5f4fb5757d6472be41a Mon Sep 17 00:00:00 2001 From: rikinsk Date: Tue, 14 May 2019 13:51:28 +0530 Subject: [PATCH 1/3] add version requirement in migration guide --- docs/graphql/manual/migrations/existing-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/graphql/manual/migrations/existing-database.rst b/docs/graphql/manual/migrations/existing-database.rst index 5d3e1fd96ec34..83418b9754b9b 100644 --- a/docs/graphql/manual/migrations/existing-database.rst +++ b/docs/graphql/manual/migrations/existing-database.rst @@ -67,7 +67,7 @@ Step 3: Initialize the migrations as per your current state ----------------------------------------------------------- Create a migration called ``init`` by exporting the current Postgres schema and -metadata from server: +metadata from server: *(available after version alpha45)* .. code-block:: bash From 4f6d7071215c35257bdfd68a2921a1457116490a Mon Sep 17 00:00:00 2001 From: rikinsk Date: Thu, 16 May 2019 11:26:21 +0530 Subject: [PATCH 2/3] add version texts --- docs/graphql/manual/event-triggers/invoke-trigger-console.rst | 2 +- docs/graphql/manual/migrations/existing-database.rst | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/graphql/manual/event-triggers/invoke-trigger-console.rst b/docs/graphql/manual/event-triggers/invoke-trigger-console.rst index 2003101fe8014..e40669d6da14f 100644 --- a/docs/graphql/manual/event-triggers/invoke-trigger-console.rst +++ b/docs/graphql/manual/event-triggers/invoke-trigger-console.rst @@ -7,7 +7,7 @@ Invoke event trigger via console :local: You can select the ``Via console`` trigger operation while :doc:`creating an event trigger <./create-trigger>` -to allow invoking the event trigger on rows manually using the Hasura console. +to allow invoking the event trigger on rows manually using the Hasura console. *(available after version beta.01)* In the ``Data -> [table-name] -> Browse Rows`` tab, clicking the invoke trigger button next to any row lets you invoke manual event triggers configured on the table with that row as payload *(the button will be shown diff --git a/docs/graphql/manual/migrations/existing-database.rst b/docs/graphql/manual/migrations/existing-database.rst index 83418b9754b9b..c6d934d183368 100644 --- a/docs/graphql/manual/migrations/existing-database.rst +++ b/docs/graphql/manual/migrations/existing-database.rst @@ -67,10 +67,11 @@ Step 3: Initialize the migrations as per your current state ----------------------------------------------------------- Create a migration called ``init`` by exporting the current Postgres schema and -metadata from server: *(available after version alpha45)* +metadata from server: .. code-block:: bash + # (available after version alpha45) # create migration files (note that this will only export public schema from postgres) hasura migrate create "init" --from-server @@ -78,6 +79,7 @@ metadata from server: *(available after version alpha45)* # mark the migration as applied on this server hasura migrate apply --version "" --skip-execution + This command will create a new "migration" under the ``migrations`` directory with the file name as ``_init.up.yaml``. This file will contain the required information to reproduce the current state of the server From d67421c1028322cffc57f268b16cd3472406ee3c Mon Sep 17 00:00:00 2001 From: rikinsk Date: Thu, 16 May 2019 11:48:09 +0530 Subject: [PATCH 3/3] add version texts --- docs/graphql/manual/deployment/allow-list.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/graphql/manual/deployment/allow-list.rst b/docs/graphql/manual/deployment/allow-list.rst index 7550e2c632dfe..66147335d684b 100644 --- a/docs/graphql/manual/deployment/allow-list.rst +++ b/docs/graphql/manual/deployment/allow-list.rst @@ -8,8 +8,7 @@ Allow-list for queries **Allow-list** is a list of safe queries (*GraphQL queries, mutations or subscriptions*) that is stored by GraphQL engine in its metadata. When enabled, it can be used to restrict GraphQL engine so that it -executes **only** those queries that are present in the list. You can also modify the allow-list without actually -enabling it on your instance. +executes **only** those queries that are present in the list *(available after version beta.01)*. Adding or removing a query in allow-list ---------------------------------------- @@ -64,6 +63,8 @@ You can add or remove a query in the allow-list in two ways: * Allow-list is stored in the metadata. To version control the state of the list, you are required to export the metadata. See :doc:`Managing Hasura metadata <../migrations/manage-metadata>` for more details. + * You can modify the allow-list without actually enabling it on your instance. + Enable allow-list -----------------