diff --git a/docs/docs/auth/authorization/permission-rules.mdx b/docs/docs/auth/authorization/permission-rules.mdx index 5e337e7e428..095f7bb01e8 100644 --- a/docs/docs/auth/authorization/permission-rules.mdx +++ b/docs/docs/auth/authorization/permission-rules.mdx @@ -933,18 +933,6 @@ When you track a table in Hasura, by default it exposes all the root fields avai you may want a role to only have access to certain root fields of a table or have the table be accessible only through [relationships](/schema/postgres/table-relationships/index.mdx). -:::info Note - -Only query and subscription root fields can be disabled. - -::: - -:::tip Supported from - -Disabling root fields is supported in version `v2.8.0` and above. - -::: - @@ -1035,6 +1023,18 @@ all fields are allowed and an empty array means no fields are allowed. +:::info Note + +Only query and subscription root fields can be disabled. + +::: + +:::tip Supported from + +Disabling root fields is supported in version `v2.8.0` and above. + +::: + #### Use cases ##### 1. Allow a table to be accessible only through a relationship diff --git a/docs/docs/databases/ms-sql-server/index.mdx b/docs/docs/databases/ms-sql-server/index.mdx index b6d77c6fa9f..a1e1b0e75a9 100644 --- a/docs/docs/databases/ms-sql-server/index.mdx +++ b/docs/docs/databases/ms-sql-server/index.mdx @@ -35,13 +35,11 @@ Here are 2 ways you can get started with Hasura and SQL Server: ## Supported features -Hasura currently supports queries, subscriptions, mutations, relationships and permissions on MS SQL Server. +Hasura currently supports queries, subscriptions, mutations, relationships, permissions, and Event Triggers on MS SQL Server. Next up on our roadmap for Hasura + SQL Server: - Support for stored procedures & custom functions ([#7073](https://github.com/hasura/graphql-engine/issues/7073)) -- Event Triggers: Trigger HTTP webhooks with atomic capture and atleast once guarantee whenever data changes inside the - database ([#7075](https://github.com/hasura/graphql-engine/issues/7075)) - Remote Joins: Join models in SQL Server to models from other API services (GraphQL or REST) ([#7076](https://github.com/hasura/graphql-engine/issues/7076)) diff --git a/docs/docs/deployment/logging.mdx b/docs/docs/deployment/logging.mdx index 151bd100c60..d28469b543c 100644 --- a/docs/docs/deployment/logging.mdx +++ b/docs/docs/deployment/logging.mdx @@ -37,12 +37,14 @@ the `type` field in a log line, which indicates which sub-system the log comes f For example, the HTTP webserver logs incoming requests as an access log and is called `http-log`. Similarly logs from the websocket layer are called `websocket-log`, logs from the Event Trigger system are called `event-trigger` etc. -You can configure the GraphQL Engine to enable/disable certain log-types using the the `--enabled-log-types` flag or the +You can configure the GraphQL Engine to enable/disable certain log-types using the `--enabled-log-types` flag or the `HASURA_GRAPHQL_ENABLED_LOG_TYPES` env var. See [GraphQL Engine server config reference](/deployment/graphql-engine-flags/reference.mdx) Default enabled log-types are: `startup, http-log, webhook-log, websocket-log, jwk-refresh-log` +### Configurable log-types + All the log-types that can be enabled/disabled are: | Log type | Description | Log Level | @@ -54,7 +56,8 @@ All the log-types that can be enabled/disabled are: | `webhook-log` | Logs responses and errors from the authorization webhook (if setup) | `info` and `error` | | `jwk-refresh-log` | Logs information and errors about periodic refreshing of JWK | `info` and `error` | -Configurable log-types + +### Internal log-types Apart from the above, there are other internal log-types which cannot be configured: @@ -68,7 +71,6 @@ Apart from the above, there are other internal log-types which cannot be configu | `schema-sync-thread` | Logs internal events, when it detects schema has changed on Postgres and when it reloads the schema | `info` and `error` | | `health-check-log` | Logs source Health Check events which includes health status of a data source | `info` and `warn` | -Internal log-types ## Logging levels diff --git a/docs/docs/mutations/postgres/upsert.mdx b/docs/docs/mutations/postgres/upsert.mdx index 0e403320cb5..d75a559b352 100644 --- a/docs/docs/mutations/postgres/upsert.mdx +++ b/docs/docs/mutations/postgres/upsert.mdx @@ -43,12 +43,6 @@ Partial unique indexes cannot be used in the `constraint` field. ::: -:::info Note - -Partial unique indexes cannot be used in the `constraint` field. - -::: - :::info Fetching Postgres constraint names You can fetch details of unique or primary key constraints on a table by running the following SQL: diff --git a/docs/docs/projects/create.mdx b/docs/docs/projects/create.mdx index cfb5c7a933f..9c9b99ce56f 100644 --- a/docs/docs/projects/create.mdx +++ b/docs/docs/projects/create.mdx @@ -38,11 +38,11 @@ Choose a pricing plan and select a region for your project. Once you have completed the project setup, click `Create Project`. -## Step 2: Database setup {#cloud-projects-db-setup} - Once created, you can specify a new name for your Project if you want. -Then to get started, Click `Launch Console` to open the Hasura Console in your browser. +## Step 2: Database setup {#cloud-projects-db-setup} + +Click `Launch Console` to open the Hasura console in your browser.