这是indexloc提供的服务，不要输入任何密码
Skip to content

add version requirement notes for features in docs #2196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 16, 2019
Merged

add version requirement notes for features in docs #2196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
449a317
add version requirement in migration guide
rikinsk May 14, 2019
0766dc4
Merge branch 'master' into docs-fix
rikinsk May 16, 2019
4f6d707
add version texts
rikinsk May 16, 2019
3a35e96
Merge branch 'master' into docs-fix
rikinsk May 16, 2019
d67421c
add version texts
rikinsk May 16, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/graphql/manual/deployment/allow-list.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
----------------------------------------
Expand Down Expand Up @@ -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
-----------------
Expand Down
2 changes: 1 addition & 1 deletion docs/graphql/manual/event-triggers/invoke-trigger-console.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 2 additions & 0 deletions docs/graphql/manual/migrations/existing-database.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,13 +71,15 @@ 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

# note down the version
# 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
Expand Down