hasura · shahidhk · May 20, 2019 · May 20, 2019 · May 20, 2019 · May 20, 2019
diff --git a/community/boilerplates/auth-servers/passportjs-jwt-roles/README.md b/community/boilerplates/auth-servers/passportjs-jwt-roles/README.md
@@ -137,7 +137,7 @@ You can also configure the server in JWKS mode and set `HASURA_GRAPHQL_JWT_SECRE
 { "type": "RS256", "jwk_url": "hostname:port/jwks" }
 ```
 
-More information in the [Hasura documentation](https://docs.hasura.io/1.0/graphql/manual/auth/jwt.html).
+More information in the [Hasura documentation](https://docs.hasura.io/1.0/graphql/manual/auth/authentication/jwt.html).
 
 ## Usage
 

diff --git a/community/boilerplates/auth-webhooks/firebase-cloud-functions/README.md b/community/boilerplates/auth-webhooks/firebase-cloud-functions/README.md
@@ -28,7 +28,7 @@ Further reading: [Firebase SDK for Cloud Functions](https://firebase.google.com/
 
 ## Create table and set permission
 
-  Follow [Common roles and auth examples](https://docs.hasura.io/1.0/graphql/manual/auth/common-roles-auth-examples.html)
+  Follow [Common roles and auth examples](https://docs.hasura.io/1.0/graphql/manual/auth/authorization/common-roles-auth-examples.html)
   on Hasura doc for details of how to setup permission to a table.
 
   Make sure to change id column of user table to TXT type as uid sent from webhook is firebase User UID format (e.g. 0LnvZc7405TjRTbjURhZYYVXPI52)

diff --git a/community/boilerplates/auth-webhooks/nodejs-express/README.md b/community/boilerplates/auth-webhooks/nodejs-express/README.md
@@ -93,7 +93,7 @@ $ now
 
 Once you have deployed this webhook, you can use it along with the GraphQL engine. You have to set the webhook URL as an environment variable in the docker container that runs the GraphQL engine.
 
-*[Read the docs](https://docs.hasura.io/1.0/graphql/manual/auth/webhook.html).*
+*[Read the docs](https://docs.hasura.io/1.0/graphql/manual/auth/authentication/webhook.html).*
 
 ### Firebase
 

diff --git a/community/boilerplates/auth-webhooks/passport-js/README.md b/community/boilerplates/auth-webhooks/passport-js/README.md
@@ -90,4 +90,4 @@ The client just need to add `Authorization: Bearer <token>` to the request sendi
 
 The endpoint (say `http://localhost:8080/webhook`) can be given as an environment variable `HASURA_GRAPHQL_AUTH_HOOK` to GraphQL Engine.
 
-[Read more about webhook here](https://docs.hasura.io/1.0/graphql/manual/auth/webhook.html).
+[Read more about webhook here](https://docs.hasura.io/1.0/graphql/manual/auth/authentication/webhook.html).
diff --git a/community/learn/graphql-tutorials/backend-services/auth-webhook/README.md b/community/learn/graphql-tutorials/backend-services/auth-webhook/README.md
@@ -6,7 +6,7 @@ This is an auth webhook for authenticating requests to the Hasura GraphQL engine
 
 Once you have deployed this webhook, you can use it along with the GraphQL engine. You have to set the webhook URL as an environment variable in the docker container that runs the GraphQL engine.
 
-*[Read the docs](https://docs.hasura.io/1.0/graphql/manual/auth/webhook.html).*
+*[Read the docs](https://docs.hasura.io/1.0/graphql/manual/auth/authentication/webhook.html).*
 
 #### Local instructions
 

@@ -8,7 +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 *(available after version beta.01)*.
+executes **only** those queries that are present in the list *(available after version v1.0.0-beta.1)*.
 
 Adding or removing a query in allow-list
 ----------------------------------------

@@ -135,7 +135,7 @@ you're already handling CORS on a reverse proxy etc.
 Load console assets from server instead of CDN
 ----------------------------------------------
 
-Starting with ``v1.0.0-beta.01``, the static assets (js, css, fonts, img etc.)
+Starting with ``v1.0.0-beta.1``, the static assets (js, css, fonts, img etc.)
 required by the console are bundled with the Docker image published by Hasura.
 These files can be found at ``/srv/console-assets``.
 

@@ -178,12 +178,12 @@ For ``serve`` sub-command these are the flags and ENV variables available:
    * - ``enable-allowlist``
      - ``HASURA_GRAPHQL_ENABLE_ALLOWLIST``
      - Restrict queries allowed to be executed by GraphQL engine to those that are part of the configured
-       allow-list. Default ``false``. *(Available for versions > v1.0.0-beta.01)*
+       allow-list. Default ``false``. *(Available for versions > v1.0.0-beta.1)*
 
    * - ``console-assets-dir``
      - ``HASURA_GRAPHQL_CONSOLE_ASSETS_DIR``
      - Set the value to ``/srv/console-assets`` for the console to load assets from the server itself
-       instead of CDN. *(Available for versions > v1.0.0-beta.01)*
+       instead of CDN. *(Available for versions > v1.0.0-beta.1)*
 
 .. note::
 

@@ -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. *(available after version beta.01)*
+to allow invoking the event trigger on rows manually using the Hasura console. *(available after version v1.0.0-beta.1)*
 
 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

@@ -71,7 +71,7 @@ metadata from server:
 
 .. code-block:: bash
 
-   # (available after version alpha45)
+   # (available after version v1.0.0-alpha45)
    # create migration files (note that this will only export public schema from postgres)
    hasura migrate create "init" --from-server
Original file line number	Diff line number	Diff line change
Expand Up		@@ -90,4 +90,4 @@ The client just need to add `Authorization: Bearer <token>` to the request sendi

		The endpoint (say `http://localhost:8080/webhook`) can be given as an environment variable `HASURA_GRAPHQL_AUTH_HOOK` to GraphQL Engine.

		[Read more about webhook here](https://docs.hasura.io/1.0/graphql/manual/auth/webhook.html).
		[Read more about webhook here](https://docs.hasura.io/1.0/graphql/manual/auth/authentication/webhook.html).