kylefang/graphql-engine
1
0
Fork 0
mirror of https://github.com/zhigang1992/graphql-engine.git synced 2026-05-25 18:32:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

add version requirement notes for features in docs (#2196)

Browse Source
This commit is contained in:
Rikin Kachhia
2019-05-16 11:49:22 +05:30
committed by Shahidh K Muhammed
parent 0b210cc245
commit 8b21ccbb0b
3 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/graphql/manual/deployment/allow-list.rst
View File

@@ -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
-----------------

2
docs/graphql/manual/event-triggers/invoke-trigger-console.rst
View File

@@ -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

2
docs/graphql/manual/migrations/existing-database.rst
View File

@@ -71,6 +71,7 @@ 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:
# mark the migration as applied on this server
hasura migrate apply --version "<version>" --skip-execution
This command will create a new "migration" under the ``migrations`` directory
with the file name as ``<timestamp(version)>_init.up.yaml``. This file will
contain the required information to reproduce the current state of the server