diff --git a/docs/docs/actions/open-api.mdx b/docs/docs/actions/open-api.mdx index ad456682250..0a000561074 100644 --- a/docs/docs/actions/open-api.mdx +++ b/docs/docs/actions/open-api.mdx @@ -17,7 +17,7 @@ import Player from '@site/src/components/Player'; # Import Action from OpenAPI Spec - + ## Introduction diff --git a/docs/docs/api-reference/cloud-api-reference.mdx b/docs/docs/api-reference/cloud-api-reference.mdx index 13356ef8b4d..8f0e3017fc1 100644 --- a/docs/docs/api-reference/cloud-api-reference.mdx +++ b/docs/docs/api-reference/cloud-api-reference.mdx @@ -17,7 +17,7 @@ import Thumbnail from '@site/src/components/Thumbnail'; # Hasura Cloud API Reference - + ## Introduction @@ -177,7 +177,7 @@ mutation createGitHubPreviewApp { | under `projectOptions`: `name` | Name of the Preview App. A Hasura Cloud project will be created with the same name. Can contain lowercase characters, numbers and hyphens. | | under `projectOptions`: `cloud` | The cloud provider to deploy the Preview App on. A Hasura Cloud project will be created in the specified cloud provider. Available: `aws` and `gcp`. | | under `projectOptions`: `region` | The region within the cloud provider to deploy the Preview App on. A Hasura Cloud project will be created in the specified region. Refer to the Hasura Cloud dashboard for available options. | -| under `projectOptions`: `plan` | Pricing tier of the created Preview App. Available options: `cloud_free` and `cloud_payg` (corresponds to Free Tier and Standard Tier respectively). | +| under `projectOptions`: `plan` | Pricing tier of the created Preview App. Available options: `cloud_free` and `cloud_payg` (corresponds to Free Tier and Professional Tier respectively). | | under `projectOptions`: `envVars` | ENV vars to be set for the created Preview App. | #### Output Fields diff --git a/docs/docs/api-reference/metadata-api/api-limits.mdx b/docs/docs/api-reference/metadata-api/api-limits.mdx index efeaea18bb9..f007d42fa6b 100644 --- a/docs/docs/api-reference/metadata-api/api-limits.mdx +++ b/docs/docs/api-reference/metadata-api/api-limits.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Metadata API Reference: API Limits - + ## Introduction diff --git a/docs/docs/api-reference/metadata-api/event-triggers.mdx b/docs/docs/api-reference/metadata-api/event-triggers.mdx index 1fe43377423..2f3072846cb 100644 --- a/docs/docs/api-reference/metadata-api/event-triggers.mdx +++ b/docs/docs/api-reference/metadata-api/event-triggers.mdx @@ -521,7 +521,7 @@ X-Hasura-Role: admin ## cleanup_event_trigger_logs {#metadata-cleanup-event-trigger-logs} - + `cleanup_event_trigger_logs` is used to manually delete the event logs for a given Event Trigger. diff --git a/docs/docs/api-reference/metadata-api/observability.mdx b/docs/docs/api-reference/metadata-api/observability.mdx index 0a16599208c..d5d0a4dae9b 100644 --- a/docs/docs/api-reference/metadata-api/observability.mdx +++ b/docs/docs/api-reference/metadata-api/observability.mdx @@ -23,7 +23,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Metadata API Reference: Observability Options - + ## Introduction @@ -31,7 +31,7 @@ The API to manage `Observability` related metadata configurations. ## Logs and metrics configuration - + These are the configurations that govern the metrics and logging output for debugging and analytics. diff --git a/docs/docs/api-reference/source-health.mdx b/docs/docs/api-reference/source-health.mdx index d7fb801c28a..c4c50bb121a 100644 --- a/docs/docs/api-reference/source-health.mdx +++ b/docs/docs/api-reference/source-health.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Source Health Check API Reference - + ## Introduction diff --git a/docs/docs/auth/authentication/multiple-admin-secrets.mdx b/docs/docs/auth/authentication/multiple-admin-secrets.mdx index beb47670cb5..1700f010846 100644 --- a/docs/docs/auth/authentication/multiple-admin-secrets.mdx +++ b/docs/docs/auth/authentication/multiple-admin-secrets.mdx @@ -1,6 +1,6 @@ --- description: Hasura Cloud and Hasura Enterprise multiple admin secrets -title: 'Cloud Standard & Enterprise Edition: Multiple Admin Secrets' +title: 'Cloud Professional & Enterprise Edition: Multiple Admin Secrets' keywords: - hasura - docs @@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Multiple Admin Secrets - + ## Introduction diff --git a/docs/docs/auth/authentication/multiple-jwt-secrets.mdx b/docs/docs/auth/authentication/multiple-jwt-secrets.mdx index 3fa85aac2e4..276e4463110 100644 --- a/docs/docs/auth/authentication/multiple-jwt-secrets.mdx +++ b/docs/docs/auth/authentication/multiple-jwt-secrets.mdx @@ -1,6 +1,6 @@ --- description: Hasura Cloud and Hasura Enterprise multiple JWT Secrets -title: 'Cloud Standard & Enterprise Edition: Multiple JWT Secrets' +title: 'Cloud Professional & Enterprise Edition: Multiple JWT Secrets' keywords: - hasura - docs @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Multiple JWT Secrets - + ## Introduction diff --git a/docs/docs/auth/authentication/webhook.mdx b/docs/docs/auth/authentication/webhook.mdx index 8834e82fa23..72df9c192f3 100644 --- a/docs/docs/auth/authentication/webhook.mdx +++ b/docs/docs/auth/authentication/webhook.mdx @@ -244,7 +244,7 @@ auth-webhook is made after the time specified in those fields and a new websocke ## Webhook Auth Caching - + Session variables from a webhook token can be cached to improve the performance of the request. diff --git a/docs/docs/caching/caching-config.mdx b/docs/docs/caching/caching-config.mdx index 3e4d51d0318..d116c01e127 100644 --- a/docs/docs/caching/caching-config.mdx +++ b/docs/docs/caching/caching-config.mdx @@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Caching Config - + ## Introduction diff --git a/docs/docs/caching/enterprise-caching.mdx b/docs/docs/caching/enterprise-caching.mdx index 728195450b4..f49cf6fc924 100644 --- a/docs/docs/caching/enterprise-caching.mdx +++ b/docs/docs/caching/enterprise-caching.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Enable Caching in Hasura Enterprise Edition - + ## Introduction diff --git a/docs/docs/caching/overview.mdx b/docs/docs/caching/overview.mdx index bc5fbaa7a75..276c52ad339 100644 --- a/docs/docs/caching/overview.mdx +++ b/docs/docs/caching/overview.mdx @@ -19,7 +19,7 @@ import Caching from '@site/static/icons/features/caching.svg'; # Hasura Caching - +
diff --git a/docs/docs/cloud-ci-cd/github-integration.mdx b/docs/docs/cloud-ci-cd/github-integration.mdx index 26e31424258..b2261d46840 100644 --- a/docs/docs/cloud-ci-cd/github-integration.mdx +++ b/docs/docs/cloud-ci-cd/github-integration.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # GitHub Deployment - + ## Introduction diff --git a/docs/docs/cloud-ci-cd/index.mdx b/docs/docs/cloud-ci-cd/index.mdx index 393d6cf8fe6..1599395ac22 100644 --- a/docs/docs/cloud-ci-cd/index.mdx +++ b/docs/docs/cloud-ci-cd/index.mdx @@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Continuous Integration and Continuous Deployment with Hasura Cloud - + ## Introduction diff --git a/docs/docs/cloud-ci-cd/one-click-deploy/create-one-click-to-deploy-apps.mdx b/docs/docs/cloud-ci-cd/one-click-deploy/create-one-click-to-deploy-apps.mdx index 959ef87f60d..ce879105f40 100644 --- a/docs/docs/cloud-ci-cd/one-click-deploy/create-one-click-to-deploy-apps.mdx +++ b/docs/docs/cloud-ci-cd/one-click-deploy/create-one-click-to-deploy-apps.mdx @@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Create a One Click Deploy to Hasura Cloud App - + ## Introduction diff --git a/docs/docs/cloud-ci-cd/one-click-deploy/index.mdx b/docs/docs/cloud-ci-cd/one-click-deploy/index.mdx index 6545f44b60c..a8b065ea36c 100644 --- a/docs/docs/cloud-ci-cd/one-click-deploy/index.mdx +++ b/docs/docs/cloud-ci-cd/one-click-deploy/index.mdx @@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # One Click Deploy to Hasura Cloud - + ## Introduction diff --git a/docs/docs/cloud-ci-cd/preview-apps.mdx b/docs/docs/cloud-ci-cd/preview-apps.mdx index a97e8d31d9b..d16d158327f 100644 --- a/docs/docs/cloud-ci-cd/preview-apps.mdx +++ b/docs/docs/cloud-ci-cd/preview-apps.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Preview Apps - + ## TL;DR diff --git a/docs/docs/cloud-ci-cd/regression-tests.mdx b/docs/docs/cloud-ci-cd/regression-tests.mdx index c42ece30259..e0e619e1a74 100644 --- a/docs/docs/cloud-ci-cd/regression-tests.mdx +++ b/docs/docs/cloud-ci-cd/regression-tests.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Regression Tests on Hasura Cloud - + ## Introduction diff --git a/docs/docs/data-federation/schema-registry.mdx b/docs/docs/data-federation/schema-registry.mdx index a9e325adcbb..b3c268c38c8 100644 --- a/docs/docs/data-federation/schema-registry.mdx +++ b/docs/docs/data-federation/schema-registry.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Schema Registry - + ## Introduction diff --git a/docs/docs/databases/database-config/cloud-connection-pooling.mdx b/docs/docs/databases/database-config/cloud-connection-pooling.mdx index ce4e539ef86..56ebd330af4 100644 --- a/docs/docs/databases/database-config/cloud-connection-pooling.mdx +++ b/docs/docs/databases/database-config/cloud-connection-pooling.mdx @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Elastic Connection Pools - + ## Introduction diff --git a/docs/docs/databases/database-config/data-connector-config.mdx b/docs/docs/databases/database-config/data-connector-config.mdx index 79cdabde4ba..e05bd20dd3c 100644 --- a/docs/docs/databases/database-config/data-connector-config.mdx +++ b/docs/docs/databases/database-config/data-connector-config.mdx @@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Data Connector Config - + ## Introduction diff --git a/docs/docs/databases/database-config/read-replicas.mdx b/docs/docs/databases/database-config/read-replicas.mdx index cdd97b664d1..81e48daf235 100644 --- a/docs/docs/databases/database-config/read-replicas.mdx +++ b/docs/docs/databases/database-config/read-replicas.mdx @@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Read Replicas - + ## Introduction diff --git a/docs/docs/databases/mariadb/cloud.mdx b/docs/docs/databases/mariadb/cloud.mdx index 53a31426b1f..0ac85ebb9aa 100644 --- a/docs/docs/databases/mariadb/cloud.mdx +++ b/docs/docs/databases/mariadb/cloud.mdx @@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Getting Started with MariaDB in Hasura Cloud - + ## Introduction diff --git a/docs/docs/databases/mariadb/index.mdx b/docs/docs/databases/mariadb/index.mdx index 280eaf26e90..235551fac24 100644 --- a/docs/docs/databases/mariadb/index.mdx +++ b/docs/docs/databases/mariadb/index.mdx @@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # MariaDB - + ## Introduction diff --git a/docs/docs/databases/mongodb/cloud.mdx b/docs/docs/databases/mongodb/cloud.mdx index 110d638df52..94b98684b6e 100644 --- a/docs/docs/databases/mongodb/cloud.mdx +++ b/docs/docs/databases/mongodb/cloud.mdx @@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Get Started with MongoDB in Hasura Cloud - + ## Introduction diff --git a/docs/docs/databases/mongodb/index.mdx b/docs/docs/databases/mongodb/index.mdx index 1112987c732..81dbe308551 100644 --- a/docs/docs/databases/mongodb/index.mdx +++ b/docs/docs/databases/mongodb/index.mdx @@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # MongoDB - + ## Introduction diff --git a/docs/docs/databases/mysql/cloud.mdx b/docs/docs/databases/mysql/cloud.mdx index 877c17b1e4b..05aa9fb0aeb 100644 --- a/docs/docs/databases/mysql/cloud.mdx +++ b/docs/docs/databases/mysql/cloud.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Getting Started with MySQL in Hasura Cloud
- +
## Introduction diff --git a/docs/docs/databases/mysql/index.mdx b/docs/docs/databases/mysql/index.mdx index 751483a9c63..0ab5c9c7abc 100644 --- a/docs/docs/databases/mysql/index.mdx +++ b/docs/docs/databases/mysql/index.mdx @@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # MySQL
- +
## Introduction @@ -54,152 +54,157 @@ schema.
- - - - - - - - - - - - - - - - - -
FeatureMySQL
Remote Relationships✅
Views✅
Default Values✅
+{' '} + + + + + + + + + + + + + + + + + +
FeatureMySQL
Remote Relationships✅
Views✅
Default Values✅
- ### Queries +### Queries - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FeatureMySQL
Simple✅
Nested Object✅
Aggregation✅
Filter / Search✅
Sort✅
Distinct✅
Paginate✅
Multiple Arguments✅
Multiple Queries✅
Variables / Aliases / Fragments✅
+{' '} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureMySQL
Simple✅
Nested Object✅
Aggregation✅
Filter / Search✅
Sort✅
Distinct✅
Paginate✅
Multiple Arguments✅
Multiple Queries✅
Variables / Aliases / Fragments✅
- ### Mutations +### Mutations - - - - - - - - - - - - - - - - - - - - - - - - - -
FeatureMySQL
Insert✅
Upsert✅
Update✅
Delete✅
Multiple per Request✅
+{' '} + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureMySQL
Insert✅
Upsert✅
Update✅
Delete✅
Multiple per Request✅
- ### Subscriptions +### Subscriptions - - - - - - - - - - - - - - - - - - - - - -
FeatureMySQL
Value of Field❌
Updates to Rows❌
Value of Derived Field❌
Streaming Subscriptions❌
+{' '} + + + + + + + + + + + + + + + + + + + + + +
FeatureMySQL
Value of Field❌
Updates to Rows❌
Value of Derived Field❌
Streaming Subscriptions❌
- ### Event Triggers +### Event Triggers - - - - - - - - - - - - - - - - - - - - - -
FeatureMySQL
INSERT❌
UPDATE❌
DELETE❌
MANUAL❌
+{' '} + + + + + + + + + + + + + + + + + + + + + +
FeatureMySQL
INSERT❌
UPDATE❌
DELETE❌
MANUAL❌
diff --git a/docs/docs/databases/oracle/cloud.mdx b/docs/docs/databases/oracle/cloud.mdx index 47f76a028a0..6349d40445d 100644 --- a/docs/docs/databases/oracle/cloud.mdx +++ b/docs/docs/databases/oracle/cloud.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Getting Started with Oracle in Hasura Cloud
- +
## Introduction diff --git a/docs/docs/databases/oracle/index.mdx b/docs/docs/databases/oracle/index.mdx index 36fa57fcb2c..53e66ee1087 100644 --- a/docs/docs/databases/oracle/index.mdx +++ b/docs/docs/databases/oracle/index.mdx @@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Oracle
- +
## Introduction @@ -51,152 +51,157 @@ schema.
- - - - - - - - - - - - - - - - - -
FeatureOracle
Remote Relationships✅
Views✅
Default Values✅
+{' '} + + + + + + + + + + + + + + + + + +
FeatureOracle
Remote Relationships✅
Views✅
Default Values✅
- ### Queries +### Queries - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FeatureOracle
Simple✅
Nested Object✅
Aggregation✅
Filter / Search✅
Sort✅
Distinct✅
Paginate✅
Multiple Arguments✅
Multiple Queries✅
Variables / Aliases / Fragments✅
+{' '} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureOracle
Simple✅
Nested Object✅
Aggregation✅
Filter / Search✅
Sort✅
Distinct✅
Paginate✅
Multiple Arguments✅
Multiple Queries✅
Variables / Aliases / Fragments✅
- ### Mutations +### Mutations - - - - - - - - - - - - - - - - - - - - - - - - - -
FeatureOracle
Insert✅
Upsert✅
Update✅
Delete✅
Multiple per Request✅
+{' '} + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureOracle
Insert✅
Upsert✅
Update✅
Delete✅
Multiple per Request✅
- ### Subscriptions +### Subscriptions - - - - - - - - - - - - - - - - - - - - - -
FeatureOracle
Value of Field❌
Updates to Rows❌
Value of Derived Field❌
Streaming Subscriptions❌
+{' '} + + + + + + + + + + + + + + + + + + + + + +
FeatureOracle
Value of Field❌
Updates to Rows❌
Value of Derived Field❌
Streaming Subscriptions❌
- ### Event Triggers +### Event Triggers - - - - - - - - - - - - - - - - - - - - - -
FeatureOracle
INSERT❌
UPDATE❌
DELETE❌
MANUAL❌
+{' '} + + + + + + + + + + + + + + + + + + + + + +
FeatureOracle
INSERT❌
UPDATE❌
DELETE❌
MANUAL❌
diff --git a/docs/docs/deployment/graphql-engine-flags/reference.mdx b/docs/docs/deployment/graphql-engine-flags/reference.mdx index 24eb6ba9692..d78ea604435 100644 --- a/docs/docs/deployment/graphql-engine-flags/reference.mdx +++ b/docs/docs/deployment/graphql-engine-flags/reference.mdx @@ -645,7 +645,7 @@ The [maximum cache size](/caching/enterprise-caching.mdx), measured in MB, for q | **Env var** | `HASURA_GRAPHQL_MAX_CACHE_SIZE` | | **Accepted values** | Integer (Representing cache size measured in MB) | | **Default** | `1` | -| **Supported in** | **Enterprise Edition**, **Cloud**: Standard / Professional tier is set to `100` MB as the default | +| **Supported in** | **Enterprise Edition**, **Cloud**: Professional tier is set to `100` MB as the default | ### Metadata Database Extension Schema diff --git a/docs/docs/deployment/health-checks/source-health-check.mdx b/docs/docs/deployment/health-checks/source-health-check.mdx index a36a86cd4d3..97d751fe9bf 100644 --- a/docs/docs/deployment/health-checks/source-health-check.mdx +++ b/docs/docs/deployment/health-checks/source-health-check.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Source Health Check - + ## Introduction diff --git a/docs/docs/getting-started/getting-started-cloud.mdx b/docs/docs/getting-started/getting-started-cloud.mdx index 767c5b7fd11..e9522f2393d 100644 --- a/docs/docs/getting-started/getting-started-cloud.mdx +++ b/docs/docs/getting-started/getting-started-cloud.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Quickstart with Hasura Cloud - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/billing/billing-owner.mdx b/docs/docs/hasura-cloud/account-management/billing/billing-owner.mdx index f622a34da67..32b8fb58a30 100644 --- a/docs/docs/hasura-cloud/account-management/billing/billing-owner.mdx +++ b/docs/docs/hasura-cloud/account-management/billing/billing-owner.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Billing Owner - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/billing/credits.mdx b/docs/docs/hasura-cloud/account-management/billing/credits.mdx index a2041095f4e..d56c1431894 100644 --- a/docs/docs/hasura-cloud/account-management/billing/credits.mdx +++ b/docs/docs/hasura-cloud/account-management/billing/credits.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Coupons and Credits - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/billing/index.mdx b/docs/docs/hasura-cloud/account-management/billing/index.mdx index 887c2a6553d..407fbcf73e0 100644 --- a/docs/docs/hasura-cloud/account-management/billing/index.mdx +++ b/docs/docs/hasura-cloud/account-management/billing/index.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Billing - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/billing/payment-methods.mdx b/docs/docs/hasura-cloud/account-management/billing/payment-methods.mdx index a91710dae5c..c3dbffc13b8 100644 --- a/docs/docs/hasura-cloud/account-management/billing/payment-methods.mdx +++ b/docs/docs/hasura-cloud/account-management/billing/payment-methods.mdx @@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Manage Payment Methods - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/billing/receipts.mdx b/docs/docs/hasura-cloud/account-management/billing/receipts.mdx index 4e238998061..9bbcdc05933 100644 --- a/docs/docs/hasura-cloud/account-management/billing/receipts.mdx +++ b/docs/docs/hasura-cloud/account-management/billing/receipts.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Receipts - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/email-change.mdx b/docs/docs/hasura-cloud/account-management/email-change.mdx index 90f2089bfc9..5a9deb4d4c7 100644 --- a/docs/docs/hasura-cloud/account-management/email-change.mdx +++ b/docs/docs/hasura-cloud/account-management/email-change.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Change Email Address - + ## Introduction diff --git a/docs/docs/hasura-cloud/account-management/index.mdx b/docs/docs/hasura-cloud/account-management/index.mdx index 52456272eb7..b7c0af9dd46 100644 --- a/docs/docs/hasura-cloud/account-management/index.mdx +++ b/docs/docs/hasura-cloud/account-management/index.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Account Management - + ## Introduction diff --git a/docs/docs/hasura-cloud/domains.mdx b/docs/docs/hasura-cloud/domains.mdx index 3b2fcfb0fca..7368a540566 100644 --- a/docs/docs/hasura-cloud/domains.mdx +++ b/docs/docs/hasura-cloud/domains.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Custom Domains - + ## Introduction diff --git a/docs/docs/hasura-cloud/environments.mdx b/docs/docs/hasura-cloud/environments.mdx index 47b61821aa5..80978a6a65b 100644 --- a/docs/docs/hasura-cloud/environments.mdx +++ b/docs/docs/hasura-cloud/environments.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Manage Development Environments - + ## Introduction @@ -105,9 +105,9 @@ Also add any other ENV vars that you might have set on your local project. ### Setting up a Git repo for your Hasura Project In order to easily apply your local changes to your new Cloud project, we'll use the Hasura -[GitHub deployment](/cloud-ci-cd/github-integration.mdx) feature. But before we do that, we need to setup -Metadata & Migrations of your local setup that you can apply to your Cloud project. For a lowdown on Hasura Metadata & -Migrations refer the guide [here](/migrations-metadata-seeds/overview.mdx) +[GitHub deployment](/cloud-ci-cd/github-integration.mdx) feature. But before we do that, we need to setup Metadata & +Migrations of your local setup that you can apply to your Cloud project. For a lowdown on Hasura Metadata & Migrations +refer the guide [here](/migrations-metadata-seeds/overview.mdx) ### Step 1: Install Hasura CLI diff --git a/docs/docs/hasura-cloud/graphql-api-explorer.mdx b/docs/docs/hasura-cloud/graphql-api-explorer.mdx index 8a7433a2cd4..242b411a880 100644 --- a/docs/docs/hasura-cloud/graphql-api-explorer.mdx +++ b/docs/docs/hasura-cloud/graphql-api-explorer.mdx @@ -22,7 +22,7 @@ import Explorer from '@site/static/icons/features/graphql_api_explorer_2.svg'; # Hasura GraphQL API Explorer - + ## TL;DR diff --git a/docs/docs/hasura-cloud/heroku-url-sync.mdx b/docs/docs/hasura-cloud/heroku-url-sync.mdx index fe52a138f29..b62a4028fa4 100644 --- a/docs/docs/hasura-cloud/heroku-url-sync.mdx +++ b/docs/docs/hasura-cloud/heroku-url-sync.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Heroku Database Integration - + :::info Note diff --git a/docs/docs/hasura-cloud/high-availability.mdx b/docs/docs/hasura-cloud/high-availability.mdx index abcf6751ff8..efb3563a7de 100644 --- a/docs/docs/hasura-cloud/high-availability.mdx +++ b/docs/docs/hasura-cloud/high-availability.mdx @@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # High-Availability Configuration - + ## Introduction diff --git a/docs/docs/hasura-cloud/plans.mdx b/docs/docs/hasura-cloud/plans.mdx index 79b40c8639b..db902069ee7 100644 --- a/docs/docs/hasura-cloud/plans.mdx +++ b/docs/docs/hasura-cloud/plans.mdx @@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Plans and Pricing - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/collaborators.mdx b/docs/docs/hasura-cloud/projects/collaborators.mdx index b8c72579115..3f2149a133d 100644 --- a/docs/docs/hasura-cloud/projects/collaborators.mdx +++ b/docs/docs/hasura-cloud/projects/collaborators.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Project Collaborators - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/create.mdx b/docs/docs/hasura-cloud/projects/create.mdx index ca1adb26bf5..ca760fcd977 100644 --- a/docs/docs/hasura-cloud/projects/create.mdx +++ b/docs/docs/hasura-cloud/projects/create.mdx @@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Create Projects - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/delete.mdx b/docs/docs/hasura-cloud/projects/delete.mdx index de0d4514549..27a8dc3f354 100644 --- a/docs/docs/hasura-cloud/projects/delete.mdx +++ b/docs/docs/hasura-cloud/projects/delete.mdx @@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Delete Projects - + ## Overview diff --git a/docs/docs/hasura-cloud/projects/details.mdx b/docs/docs/hasura-cloud/projects/details.mdx index feb6b2c487b..7384e581be6 100644 --- a/docs/docs/hasura-cloud/projects/details.mdx +++ b/docs/docs/hasura-cloud/projects/details.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Project Details - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/env-vars.mdx b/docs/docs/hasura-cloud/projects/env-vars.mdx index 140b7cce876..46c92029c8a 100644 --- a/docs/docs/hasura-cloud/projects/env-vars.mdx +++ b/docs/docs/hasura-cloud/projects/env-vars.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Project Env Vars - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/hibernation.mdx b/docs/docs/hasura-cloud/projects/hibernation.mdx index b41a9f9017d..e0cb75e19ee 100644 --- a/docs/docs/hasura-cloud/projects/hibernation.mdx +++ b/docs/docs/hasura-cloud/projects/hibernation.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Project Hibernation and Reactivation - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/index.mdx b/docs/docs/hasura-cloud/projects/index.mdx index 8ac55fab44c..5a4955b35df 100644 --- a/docs/docs/hasura-cloud/projects/index.mdx +++ b/docs/docs/hasura-cloud/projects/index.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Projects & Collaborators - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/maintenance-mode.mdx b/docs/docs/hasura-cloud/projects/maintenance-mode.mdx index df7baa020d2..dd478303899 100644 --- a/docs/docs/hasura-cloud/projects/maintenance-mode.mdx +++ b/docs/docs/hasura-cloud/projects/maintenance-mode.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Maintenance Mode - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/move-project-manual.mdx b/docs/docs/hasura-cloud/projects/move-project-manual.mdx index e2675d89142..3492516aedf 100644 --- a/docs/docs/hasura-cloud/projects/move-project-manual.mdx +++ b/docs/docs/hasura-cloud/projects/move-project-manual.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Transfer Existing Hasura Cloud Project to a New Project - + ## Introduction @@ -64,15 +64,14 @@ See [deleting projects](/hasura-cloud/projects/delete.mdx) to delete the earlier - You can [rename](/hasura-cloud/projects/details.mdx#rename-project) your new project to the same name as the earlier project if you wish. -- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/domains.mdx) for your - project, you might want to update any clients consuming the GraphQL API to point to the new project's GraphQL - endpoint. +- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/domains.mdx) for your project, you + might want to update any clients consuming the GraphQL API to point to the new project's GraphQL endpoint. ## Zero-downtime transfer -To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/domains.mdx) -attached to your Cloud project. Once the new project is set up identically as the old one, you can update the DNS -entries for your custom domain to the new project to have a seamless transfer of traffic to the new project. +To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/domains.mdx) attached to your +Cloud project. Once the new project is set up identically as the old one, you can update the DNS entries for your custom +domain to the new project to have a seamless transfer of traffic to the new project. If you simply want to avoid updating your clients with the new project's API endpoint, you can simply [rename](/hasura-cloud/projects/details.mdx#rename-project) your new project with the same name as the earlier project. diff --git a/docs/docs/hasura-cloud/projects/move-project-v2-manual.mdx b/docs/docs/hasura-cloud/projects/move-project-v2-manual.mdx index 84cc8323257..143fb0b68fa 100644 --- a/docs/docs/hasura-cloud/projects/move-project-v2-manual.mdx +++ b/docs/docs/hasura-cloud/projects/move-project-v2-manual.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Manually Move Hasura Cloud v1.3 Projects to Hasura v2.0 - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/move-project-v2.mdx b/docs/docs/hasura-cloud/projects/move-project-v2.mdx index a311d027de9..3fe7c613a4e 100644 --- a/docs/docs/hasura-cloud/projects/move-project-v2.mdx +++ b/docs/docs/hasura-cloud/projects/move-project-v2.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Updating Hasura Cloud v1.3 Projects to Hasura v2.0 - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/ownership.mdx b/docs/docs/hasura-cloud/projects/ownership.mdx index 9c2d4e376a4..4f9ffb258f2 100644 --- a/docs/docs/hasura-cloud/projects/ownership.mdx +++ b/docs/docs/hasura-cloud/projects/ownership.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Transfer Project Ownership - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/pricing.mdx b/docs/docs/hasura-cloud/projects/pricing.mdx index 11fcf858969..617b02be45b 100644 --- a/docs/docs/hasura-cloud/projects/pricing.mdx +++ b/docs/docs/hasura-cloud/projects/pricing.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Switch Pricing Plans - + ## Introduction Hasura has different pricing plans that you can choose from based on your requirements. This page explains how to switch @@ -54,7 +54,7 @@ Go to `Projects` and click on the project you'd like to change. Now click on the `Usage tab`. To upgrade to the `Professional` plan, click on the `Upgrade` button: - + Your project is now running on the `Professional` plan. @@ -64,7 +64,7 @@ Go to `Projects` and click on the project you'd like to change. Under the `General` tab, find the `Pricing tier` section and click on the edit icon on the right: - + You'll be charged as per the `Professional` plan until the end of the day. From the next day onwards, the project will be on the `Free` tier. If the `Free` tier limit is exhausted, the project might become inactive. diff --git a/docs/docs/hasura-cloud/projects/recover.mdx b/docs/docs/hasura-cloud/projects/recover.mdx index 6562d43dbb4..941fda7fb2a 100644 --- a/docs/docs/hasura-cloud/projects/recover.mdx +++ b/docs/docs/hasura-cloud/projects/recover.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Recover Project - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/regions.mdx b/docs/docs/hasura-cloud/projects/regions.mdx index d3c0fc1e0d3..066bf2e281c 100644 --- a/docs/docs/hasura-cloud/projects/regions.mdx +++ b/docs/docs/hasura-cloud/projects/regions.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Deployment Regions - + ## Introduction diff --git a/docs/docs/hasura-cloud/projects/secure.mdx b/docs/docs/hasura-cloud/projects/secure.mdx index 1fbd449fb99..946f03ec044 100644 --- a/docs/docs/hasura-cloud/projects/secure.mdx +++ b/docs/docs/hasura-cloud/projects/secure.mdx @@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Secure Projects - + ## Introduction diff --git a/docs/docs/hasura-cloud/regions.mdx b/docs/docs/hasura-cloud/regions.mdx index 2e803f9ef0d..3bb706914d1 100644 --- a/docs/docs/hasura-cloud/regions.mdx +++ b/docs/docs/hasura-cloud/regions.mdx @@ -14,12 +14,13 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Regions - + ## Introduction -Hasura Cloud is available in multiple regions on both Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure Cloud. This -allows you to choose the region that is closest to your users to reduce latency and improve performance. +Hasura Cloud is available in multiple regions on both Amazon Web Services (AWS), Google Cloud Platform (GCP) and +Microsoft Azure Cloud. This allows you to choose the region that is closest to your users to reduce latency and improve +performance. ## Supported regions @@ -47,7 +48,6 @@ allows you to choose the region that is closest to your users to reduce latency - Frankfurt, Germany - St. Ghislain, Belgium - ### Azure Cloud (Azure) - US East (Virginia) diff --git a/docs/docs/hasura-cloud/vercel-integration.mdx b/docs/docs/hasura-cloud/vercel-integration.mdx index d2a86ed4b31..75c8ec36843 100644 --- a/docs/docs/hasura-cloud/vercel-integration.mdx +++ b/docs/docs/hasura-cloud/vercel-integration.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Vercel Integration - + ## Introduction @@ -155,9 +155,9 @@ Your integration will only be successfully configured upon clicking the `Install :::info Note -- If a [custom domain](/hasura-cloud/domains.mdx) is added to the Hasura Cloud project, you'll have to set this - custom value to `HASURA_PROJECT_ENDPOINT` and `NEXT_HASURA_PROJECT_ENDPOINT` manually in the respective Vercel - project's settings. +- If a [custom domain](/hasura-cloud/domains.mdx) is added to the Hasura Cloud project, you'll have to set this custom + value to `HASURA_PROJECT_ENDPOINT` and `NEXT_HASURA_PROJECT_ENDPOINT` manually in the respective Vercel project's + settings. - Similarly if the Hasura Cloud project's admin secret is changed, you will have to edit the `HASURA_ADMIN_SECRET` manually in the respective Vercel project's settings. diff --git a/docs/docs/observability/cloud-monitoring/errors.mdx b/docs/docs/observability/cloud-monitoring/errors.mdx index 907c8f979e1..5f82014d46b 100644 --- a/docs/docs/observability/cloud-monitoring/errors.mdx +++ b/docs/docs/observability/cloud-monitoring/errors.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Errors - + ## Introduction diff --git a/docs/docs/observability/cloud-monitoring/operations.mdx b/docs/docs/observability/cloud-monitoring/operations.mdx index ff8d028f6b3..52d7c5607d2 100644 --- a/docs/docs/observability/cloud-monitoring/operations.mdx +++ b/docs/docs/observability/cloud-monitoring/operations.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Operations - + ## Introduction diff --git a/docs/docs/observability/cloud-monitoring/subscription-workers.mdx b/docs/docs/observability/cloud-monitoring/subscription-workers.mdx index b38f7c48b59..32e6dc375e2 100644 --- a/docs/docs/observability/cloud-monitoring/subscription-workers.mdx +++ b/docs/docs/observability/cloud-monitoring/subscription-workers.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Subscription Workers - + ## Introduction diff --git a/docs/docs/observability/cloud-monitoring/tracing.mdx b/docs/docs/observability/cloud-monitoring/tracing.mdx index 33a8cc3120d..77a02e23316 100644 --- a/docs/docs/observability/cloud-monitoring/tracing.mdx +++ b/docs/docs/observability/cloud-monitoring/tracing.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Distributed Tracing - + ## Introduction diff --git a/docs/docs/observability/cloud-monitoring/usage.mdx b/docs/docs/observability/cloud-monitoring/usage.mdx index 35a11265a6a..2e8a9c67104 100644 --- a/docs/docs/observability/cloud-monitoring/usage.mdx +++ b/docs/docs/observability/cloud-monitoring/usage.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Usage Summaries - + ## Introduction diff --git a/docs/docs/observability/cloud-monitoring/websockets.mdx b/docs/docs/observability/cloud-monitoring/websockets.mdx index 8c65d0e7e54..b4d15243c6e 100644 --- a/docs/docs/observability/cloud-monitoring/websockets.mdx +++ b/docs/docs/observability/cloud-monitoring/websockets.mdx @@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Websockets - + ## Overview diff --git a/docs/docs/observability/cloud/azure-monitor.mdx b/docs/docs/observability/cloud/azure-monitor.mdx index a7169d2b8b0..a1ad7c1051d 100644 --- a/docs/docs/observability/cloud/azure-monitor.mdx +++ b/docs/docs/observability/cloud/azure-monitor.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Azure Monitor Integration on Hasura Cloud - + ## Introduction diff --git a/docs/docs/observability/cloud/datadog.mdx b/docs/docs/observability/cloud/datadog.mdx index 1257600a549..8c7901cab90 100644 --- a/docs/docs/observability/cloud/datadog.mdx +++ b/docs/docs/observability/cloud/datadog.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Datadog Integration on Hasura Cloud - + ## Introduction diff --git a/docs/docs/observability/cloud/index.mdx b/docs/docs/observability/cloud/index.mdx index f85665068b5..536d71f8241 100644 --- a/docs/docs/observability/cloud/index.mdx +++ b/docs/docs/observability/cloud/index.mdx @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Hasura Cloud observability integrations with external services - + ## Introduction diff --git a/docs/docs/observability/cloud/newrelic.mdx b/docs/docs/observability/cloud/newrelic.mdx index e9d0b1476fd..f17226bf6d2 100644 --- a/docs/docs/observability/cloud/newrelic.mdx +++ b/docs/docs/observability/cloud/newrelic.mdx @@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # New Relic Integration on Hasura Cloud - + ## Introduction diff --git a/docs/docs/observability/cloud/prometheus.mdx b/docs/docs/observability/cloud/prometheus.mdx index dba7d818ce8..2194fb09339 100644 --- a/docs/docs/observability/cloud/prometheus.mdx +++ b/docs/docs/observability/cloud/prometheus.mdx @@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Prometheus Integration for Hasura Cloud - + ## Introduction diff --git a/docs/docs/observability/enterprise-edition/index.mdx b/docs/docs/observability/enterprise-edition/index.mdx index 424dde66570..6a9b2843ae0 100644 --- a/docs/docs/observability/enterprise-edition/index.mdx +++ b/docs/docs/observability/enterprise-edition/index.mdx @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Hasura EE observability integrations with external services - + ## Introduction @@ -35,4 +35,3 @@ choice: - [Prometheus](prometheus/index.mdx) - [OpenTelemetry](/observability/opentelemetry.mdx) - diff --git a/docs/docs/observability/opentelemetry.mdx b/docs/docs/observability/opentelemetry.mdx index 5fc021a2f1d..b1cd844e5bd 100644 --- a/docs/docs/observability/opentelemetry.mdx +++ b/docs/docs/observability/opentelemetry.mdx @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Export Traces and Metrics to OpenTelemetry Compliant Receiver from Hasura
- +
Beta
diff --git a/docs/docs/observability/overview.mdx b/docs/docs/observability/overview.mdx index 59e4de31d41..1f803eb1695 100644 --- a/docs/docs/observability/overview.mdx +++ b/docs/docs/observability/overview.mdx @@ -17,7 +17,7 @@ import Observability from '@site/static/icons/features/observability.svg'; # Observability - +
@@ -46,7 +46,9 @@ import Observability from '@site/static/icons/features/observability.svg'; Hasura Cloud Built-in Monitoring
  • - Pre-built dashboards with Hasura EE + + Pre-built dashboards with Hasura EE +
  • Database observability diff --git a/docs/docs/observability/query-tags.mdx b/docs/docs/observability/query-tags.mdx index 3fbb2dbff0b..be311032f96 100644 --- a/docs/docs/observability/query-tags.mdx +++ b/docs/docs/observability/query-tags.mdx @@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Query Tags - + ## Introduction diff --git a/docs/docs/policies/sla.mdx b/docs/docs/policies/sla.mdx index a411985e6d6..05c2e2763d9 100644 --- a/docs/docs/policies/sla.mdx +++ b/docs/docs/policies/sla.mdx @@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Hasura Cloud Service Level Agreement (SLA) - + ## Introduction @@ -26,7 +26,7 @@ applies to paid tiers in Hasura Cloud. We calculate SLA uptime monthly and measure uptime with an HTTP request to the `/v1/version` endpoint on a project at a regular interval. -Cloud Standard and Cloud Professional users can find more detail regarding uptime in our +Cloud Professional users can find more detail regarding uptime in our [terms of service](https://hasura.io/legal/hasura-cloud-terms-of-service/). Cloud Enterprise users should reference their contracts for details. diff --git a/docs/docs/schema/bigquery/native-queries.mdx b/docs/docs/schema/bigquery/native-queries.mdx index 9e2b7f659cb..53abbd45a26 100644 --- a/docs/docs/schema/bigquery/native-queries.mdx +++ b/docs/docs/schema/bigquery/native-queries.mdx @@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail'; # BigQuery: Native Queries
    - +
    ## What are Native Queries? @@ -319,8 +319,8 @@ Once the modal is open, fill in the forms with: -You can create a logical model by adding it to the appropriate database definition in the `metadata > databases > databases.yaml` -file: +You can create a logical model by adding it to the appropriate database definition in the +`metadata > databases > databases.yaml` file: ```yaml logical_models: @@ -519,8 +519,7 @@ A future release will allow mutations to be specified using Native Queries. ## Permissions Native queries will inherit the permissions of the Logical Model that they return. See the -[documentation on Logical Models](/schema/bigquery/logical-models.mdx) for an explanation of how to add -permissions. +[documentation on Logical Models](/schema/bigquery/logical-models.mdx) for an explanation of how to add permissions. ## Relationships @@ -679,7 +678,6 @@ query { - ## Relationships with tables Relationships can be defined between tables and Native Queries residing in the same source. diff --git a/docs/docs/schema/ms-sql-server/native-queries.mdx b/docs/docs/schema/ms-sql-server/native-queries.mdx index 27bb76ec3bf..1a2c17991c6 100644 --- a/docs/docs/schema/ms-sql-server/native-queries.mdx +++ b/docs/docs/schema/ms-sql-server/native-queries.mdx @@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail'; # MS SQL Server: Native Queries
    - +
    ## What are Native Queries? @@ -325,8 +325,8 @@ Finally, add any optional fields that you would like to be included in the Logic -You can create a logical model by adding it to the appropriate database definition in the `metadata > databases > databases.yaml` -file: +You can create a logical model by adding it to the appropriate database definition in the +`metadata > databases > databases.yaml` file: ```yaml logical_models: diff --git a/docs/docs/schema/ms-sql-server/stored-procedures.mdx b/docs/docs/schema/ms-sql-server/stored-procedures.mdx index a5e852ab296..33879647a88 100644 --- a/docs/docs/schema/ms-sql-server/stored-procedures.mdx +++ b/docs/docs/schema/ms-sql-server/stored-procedures.mdx @@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail'; # MS SQL Server: Stored Procedures
    - +
    ## What are stored procedures? @@ -291,8 +291,8 @@ stored procedure.     -You can create a logical model by adding it to the appropriate database definition in the `metadata > databases > databases.yaml` -file: +You can create a logical model by adding it to the appropriate database definition in the +`metadata > databases > databases.yaml` file: ```yaml logical_models: diff --git a/docs/docs/schema/postgres/input-validations.mdx b/docs/docs/schema/postgres/input-validations.mdx index 55a80ff3e8f..adf173b7716 100644 --- a/docs/docs/schema/postgres/input-validations.mdx +++ b/docs/docs/schema/postgres/input-validations.mdx @@ -20,7 +20,7 @@ import TabItem from '@theme/TabItem'; # Postgres: Input Validations - + ## Introduction @@ -30,11 +30,11 @@ Input validations are supported for versions `v2.29.0` and above. ::: -Many times, we need to perform validations on the input arguments of a GraphQL mutation before inserting, deleting -or updating the data. +Many times, we need to perform validations on the input arguments of a GraphQL mutation before inserting, deleting or +updating the data. -Hasura provides a way to add input validations to your GraphQL mutations which route the input arguments of a -GraphQL mutation to an HTTP webhook to perform complex validation logic. +Hasura provides a way to add input validations to your GraphQL mutations which route the input arguments of a GraphQL +mutation to an HTTP webhook to perform complex validation logic. ### Example @@ -42,19 +42,20 @@ Consider you have the following GraphQL mutation: ```graphql mutation insert_users { - insert_users(objects: [{name: "John", phone: "999"}]) { + insert_users(objects: [{ name: "John", phone: "999" }]) { affected_rows } } mutation update_users { - update_users(where: {id: {_eq: 1}}, _set: {name: "John", email : "random email"}) { + update_users(where: { id: { _eq: 1 } }, _set: { name: "John", email: "random email" }) { affected_rows } } ``` You can define the input validations for the above mutations to perform the following checks: + 1. Check that the `name` field is not empty 2. Check that the `phone` field is a valid phone number 3. Check that the `email` field is a valid email address @@ -94,11 +95,10 @@ file, eg: definition: url: http://www.somedomain.com/validateProducts headers: - - name: X-Validate-Input-API-Key - value_from_env: VALIDATION_HOOK_API_KEY + - name: X-Validate-Input-API-Key + value_from_env: VALIDATION_HOOK_API_KEY forward_client_headers: true timeout: 5 - ``` Apply the Metadata by running: @@ -110,8 +110,8 @@ hasura metadata apply -You can define the input validations when using the [permissions Metadata API](/api-reference/metadata-api/permission.mdx). -Example with a Postgres DB: +You can define the input validations when using the +[permissions Metadata API](/api-reference/metadata-api/permission.mdx). Example with a Postgres DB: ```http {14-21} POST /v1/metadata HTTP/1.1 @@ -140,29 +140,32 @@ X-Hasura-Role: admin } } ``` + The `type` determines the interface for the input validation, which initially only supports an `http` webhook URL. -The `definition` field provides the necessary context for communicating and submitting the data for input validation. -It is an object with the following fields. -- `url` - *Required*, a [string value](https://hasura.io/docs/latest/api-reference/syntax-defs/#webhookurl) which +The `definition` field provides the necessary context for communicating and submitting the data for input validation. It +is an object with the following fields. + +- `url` - _Required_, a [string value](https://hasura.io/docs/latest/api-reference/syntax-defs/#webhookurl) which supports templating environment variables. -- `headers` - *Optional*, a list of headers to be sent to the URL. -- `forward_client_headers` - *Optional*, default is `false`. If set to `true` the client headers are forwarded to - the URL. -- `timeout` - *Optional*, default is `10`. The number of seconds to wait for a response before timing out. +- `headers` - _Optional_, a list of headers to be sent to the URL. +- `forward_client_headers` - _Optional_, default is `false`. If set to `true` the client headers are forwarded to the + URL. +- `timeout` - _Optional_, default is `10`. The number of seconds to wait for a response before timing out. :::caution Reduced performance -Mutations that involve input validation **may exhibit slower performance** compared to mutations without -validation. The execution time of the webhook URL can become a bottleneck, potentially reaching the maximum limit -specified by the `timeout` configuration value, the default of which is 10 seconds. +Mutations that involve input validation **may exhibit slower performance** compared to mutations without validation. The +execution time of the webhook URL can become a bottleneck, potentially reaching the maximum limit specified by the +`timeout` configuration value, the default of which is 10 seconds. ::: ## How it works + Following are the steps that are performed by mutations types (`insert/update/delete`) When an mutation arrives with a role, the following steps are performed: @@ -171,16 +174,16 @@ When an mutation arrives with a role, the following steps are performed: nested inserts) 2. If there is a `validate_input` permission defined on a table, then any mutation arguments targeting that table are sent to the validation URL. This is done for all tables. -3. If all handlers validate the mutation arguments, then the request proceeds. **A transaction with - the database will only be started after the validation is completed and successful.** -4. If any webhook rejects the mutation data, then the request is aborted. An `error` message from the URL can also - be forwarded to the client. +3. If all handlers validate the mutation arguments, then the request proceeds. **A transaction with the database will + only be started after the validation is completed and successful.** +4. If any webhook rejects the mutation data, then the request is aborted. An `error` message from the URL can also be + forwarded to the client. Consider the following sample mutation: ```graphql -mutation insertAuthorWithArticles($name: String, $email:String, $articles_content:[article_insert_input!]!) { - insert_author(objects: {name: $name, email: $email, articles: {data: $articles_content}}){ +mutation insertAuthorWithArticles($name: String, $email: String, $articles_content: [article_insert_input!]!) { + insert_author(objects: { name: $name, email: $email, articles: { data: $articles_content } }) { returning { first_name articles { @@ -191,25 +194,25 @@ mutation insertAuthorWithArticles($name: String, $email:String, $articles_conten } ``` -The above mutation targets the `author` and `article` tables, involving a nested insert of an article into the -author model. Assuming that the `validate_input` permission is defined for both tables, the validation process -unfolds as follows: +The above mutation targets the `author` and `article` tables, involving a nested insert of an article into the author +model. Assuming that the `validate_input` permission is defined for both tables, the validation process unfolds as +follows: 1. The validation webhook specified for the `author` table is contacted first, including the inserted row with - `articles` + `articles` 2. Subsequently, the validation webhook designated for the `article` table is contacted with `$articles_content` rows. 3. If both of the above webhook calls result in successful validation, a database transaction is started to insert the rows into the respective tables. - ## Webhook specification per mutation type ### Request -When a mutation on a table with `validate_input` configuration is executed, before making a database -transaction, Hasura sends the mutation argument data to the validation HTTP webhook using a `POST` request. +When a mutation on a table with `validate_input` configuration is executed, before making a database transaction, Hasura +sends the mutation argument data to the validation HTTP webhook using a `POST` request. The request payload is of the format: + ```json { "version": "", @@ -223,8 +226,9 @@ The request payload is of the format: } } ``` -- `version`: An integer version serves to indicate the request format. Whenever a breaking update occurs in the - request payload, the version will be incremented. The initial version is set to `1`. + +- `version`: An integer version serves to indicate the request format. Whenever a breaking update occurs in the request + payload, the version will be incremented. The initial version is set to `1`. - `role`: Hasura session role on which permissions are enforced. - `session_variables`: Session variables that aid in enforcing permissions. Session variable names always starts with `x-hasura-*`. @@ -243,9 +247,9 @@ The request payload is of the format: } ``` -- `data.input`: List of rows to be inserted which are specified in the `objects` input field of insert mutation. - Also includes nested data of relationships. The structure of this field will be similar to the JSONified structure - of the `_insert_input!` graphql type. +- `data.input`: List of rows to be inserted which are specified in the `objects` input field of insert mutation. Also + includes nested data of relationships. The structure of this field will be similar to the JSONified structure of the + `_insert_input!` graphql type. Note that, in `data.input`, if the data to be inserted contains nested inserts, then: @@ -273,9 +277,10 @@ upstream webhook is expected to receive those values in the payload. } } ``` + - `data.input`: List of the multiple updates to run. The structure of this field will be similar to the JSONified - structure of the `_updates!` graphql type. If it is an update mutation by primary key, then it will - also contain the `_pk_columns_input!` + structure of the `_updates!` graphql type. If it is an update mutation by primary key, then it will also + contain the `_pk_columns_input!` #### Delete Mutations @@ -299,8 +304,8 @@ expected to receive those values in the payload. ``` - `data.input`: The delete condition. The structure of this field will be similar to the JSONified structure of the -`_bool_exp!` graphql type. If it is a delete mutation by primary key, then it will also contain the -`_pk_columns_input!` + `_bool_exp!` graphql type. If it is a delete mutation by primary key, then it will also contain the + `_pk_columns_input!` ### Response diff --git a/docs/docs/schema/snowflake/native-queries.mdx b/docs/docs/schema/snowflake/native-queries.mdx index 02ea825891f..857bd291c8d 100644 --- a/docs/docs/schema/snowflake/native-queries.mdx +++ b/docs/docs/schema/snowflake/native-queries.mdx @@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail'; # Snowflake: Native Queries
    - +
    ## What are Native Queries? @@ -208,8 +208,8 @@ native_queries: max_length: type: integer code: - SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) < {{max_length}} THEN '' - else '...' END)) AS "excerpt", date as "date" FROM article + SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) < + {{max_length}} THEN '' else '...' END)) AS "excerpt", date as "date" FROM article returns: article_excerpt ``` @@ -289,11 +289,14 @@ When we run this GraphQL query, we get the following results: :::info All fields in Snowflake are required to use `as "field"` syntax in your native query SQL -When writing your queries for Snowflake you must use `as "field"` syntax for all returning fields. From the `article` example above: +When writing your queries for Snowflake you must use `as "field"` syntax for all returning fields. From the `article` +example above: + ```sql SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) < {{max_length}} THEN '' else '...' END)) AS "excerpt", date as "date" FROM article ``` + Notice that each field that we are returning we provide the `as "field"`. ::: @@ -336,8 +339,8 @@ Finally, add any optional fields that you would like to be included in the Logic -You can create a logical model by adding it to the appropriate database definition in the `metadata > databases > databases.yaml` -file: +You can create a logical model by adding it to the appropriate database definition in the +`metadata > databases > databases.yaml` file: ```yaml logical_models: diff --git a/docs/docs/security/allow-list.mdx b/docs/docs/security/allow-list.mdx index f5472acd702..e4eb0223c35 100644 --- a/docs/docs/security/allow-list.mdx +++ b/docs/docs/security/allow-list.mdx @@ -148,7 +148,7 @@ query ($id: Int!) { ## Role-based Allow List - + A role-based Allow List is useful when you would like a query collection(s) to be accessible to only certain roles. @@ -221,7 +221,7 @@ Metadata API. ## Quick-create allowed operations - + ### Hasura Cloud diff --git a/docs/docs/security/api-limits.mdx b/docs/docs/security/api-limits.mdx index 8c19e83e4ad..00c8af86916 100644 --- a/docs/docs/security/api-limits.mdx +++ b/docs/docs/security/api-limits.mdx @@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # API Limits - + ## Introduction @@ -53,8 +53,8 @@ be used to rate-limit requests. To enable rate limiting on Hasura Enterprise, you must set the [`HASURA_GRAPHQL_RATE_LIMIT_REDIS_URL`](/deployment/graphql-engine-flags/reference.mdx#rate-limit-redis-url) environment -variable or the [`--rate-limit-redis-url`](/deployment/graphql-engine-flags/reference.mdx#rate-limit-redis-url) server flag -with the appropriate Redis connection string. +variable or the [`--rate-limit-redis-url`](/deployment/graphql-engine-flags/reference.mdx#rate-limit-redis-url) server +flag with the appropriate Redis connection string. ::: @@ -153,8 +153,8 @@ sources. :::info Time limits on Hasura Cloud projects -All Free tier and Standard tier Hasura Cloud projects get a time limit of 60 seconds. When the cloud limit is hit, the -error contains the code `tenant-time-limit-exceeded` in the error message. +All Free tier and Professional tier Hasura Cloud projects get a time limit of 60 seconds. When the cloud limit is hit, +the error contains the code `tenant-time-limit-exceeded` in the error message. ::: diff --git a/docs/docs/security/container-images.mdx b/docs/docs/security/container-images.mdx index fa349d05a59..97291b97dde 100644 --- a/docs/docs/security/container-images.mdx +++ b/docs/docs/security/container-images.mdx @@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Proactive Vulnerability Scanning of Container Images - + ## Overview diff --git a/docs/docs/security/disable-graphql-introspection.mdx b/docs/docs/security/disable-graphql-introspection.mdx index 634fb68c85b..5c783137084 100644 --- a/docs/docs/security/disable-graphql-introspection.mdx +++ b/docs/docs/security/disable-graphql-introspection.mdx @@ -1,6 +1,6 @@ --- description: Hasura Cloud and Enterprise Edition disable GraphQL introspection -title: 'Cloud Standard & Enterprise Edition: Disable GraphQL introspection' +title: 'Cloud Professional & Enterprise Edition: Disable GraphQL introspection' keywords: - hasura - docs @@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge'; # Disable GraphQL Introspection - + ## Introduction diff --git a/docs/docs/security/overview.mdx b/docs/docs/security/overview.mdx index 80a1ad91c90..058e8506fe8 100644 --- a/docs/docs/security/overview.mdx +++ b/docs/docs/security/overview.mdx @@ -1,5 +1,5 @@ --- -description: Hasura Cloud Standard and Hasura Enterprise API Security +description: Hasura Cloud Professional and Hasura Enterprise API Security title: 'Cloud & Enterprise Edition: API Security' keywords: - hasura diff --git a/docs/src/components/ProductBadge/index.tsx b/docs/src/components/ProductBadge/index.tsx index 1bcbecfc3b1..d083eda4e46 100644 --- a/docs/src/components/ProductBadge/index.tsx +++ b/docs/src/components/ProductBadge/index.tsx @@ -5,7 +5,6 @@ import VersionedLink from '@site/src/components/VersionedLink'; type ProductBadgeProps = { ce: boolean; free: boolean; - standard: boolean; pro: boolean; ee: boolean; self: boolean; @@ -28,13 +27,6 @@ function createLinks(props: ProductBadgeProps) { ); } - if (props.standard) { - links.push( - - Cloud Standard - - ); - } if (props.pro) { links.push( diff --git a/docs/wiki/style/product-badges.mdx b/docs/wiki/style/product-badges.mdx index b53ff4e248b..e38204936a0 100644 --- a/docs/wiki/style/product-badges.mdx +++ b/docs/wiki/style/product-badges.mdx @@ -24,7 +24,6 @@ order of the props doesn't matter, but the props themselves are: | ---------- | ------------------------ | | `ce` | Community Edition | | `free` | Cloud Free | -| `standard` | Cloud Standard | | `pro` | Cloud Professional | | `ee` | Cloud Enterprise Edition | | `self` | Self-Hosted EE |