hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-07-14 14:00:31 +03:00
Code Issues Projects Releases Wiki Activity

docs: remove standard cloud tier references throughout docs

Browse Source 
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10254
GitOrigin-RevId: 84e28b38e1a10eeefe207acd207bc8b584eea20d
This commit is contained in:
Rob Dominguez 2023-09-01 10:29:14 -05:00 committed by hasura-bot
parent dcf5944aa5
commit 6d7865b383
92 changed files with 469 additions and 462 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/actions/open-api.mdx
View File

@ -17,7 +17,7 @@ import Player from '@site/src/components/Player';
# Import Action from OpenAPI Spec
<ProductBadge ce free standard pro ee self />
<ProductBadge ce free pro ee self />
## Introduction

4
docs/docs/api-reference/cloud-api-reference.mdx
View File

@ -17,7 +17,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
# Hasura Cloud API Reference
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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

2
docs/docs/api-reference/metadata-api/api-limits.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Metadata API Reference: API Limits
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
## Introduction

2
docs/docs/api-reference/metadata-api/event-triggers.mdx
View File

@ -521,7 +521,7 @@ X-Hasura-Role: admin
## cleanup_event_trigger_logs {#metadata-cleanup-event-trigger-logs}
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
`cleanup_event_trigger_logs` is used to manually delete the event logs for a given Event Trigger.

4
docs/docs/api-reference/metadata-api/observability.mdx
View File

@ -23,7 +23,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Metadata API Reference: Observability Options
<ProductBadge ce free standard pro ee self />
<ProductBadge ce free pro ee self />
## Introduction
@ -31,7 +31,7 @@ The API to manage `Observability` related metadata configurations.
## Logs and metrics configuration
<ProductBadge standard pro />
<ProductBadge pro />
These are the configurations that govern the metrics and logging output for debugging and analytics.

2
docs/docs/api-reference/source-health.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Source Health Check API Reference
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

4
docs/docs/auth/authentication/multiple-admin-secrets.mdx
View File

@ -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
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

4
docs/docs/auth/authentication/multiple-jwt-secrets.mdx
View File

@ -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
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

2
docs/docs/auth/authentication/webhook.mdx
View File

@ -244,7 +244,7 @@ auth-webhook is made after the time specified in those fields and a new websocke
## Webhook Auth Caching
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
Session variables from a webhook token can be cached to improve the performance of the request.

2
docs/docs/caching/caching-config.mdx
View File

@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Caching Config
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

2
docs/docs/caching/enterprise-caching.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Enable Caching in Hasura Enterprise Edition
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

2
docs/docs/caching/overview.mdx
View File

@ -19,7 +19,7 @@ import Caching from '@site/static/icons/features/caching.svg';
# <Caching /> Hasura Caching
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
<div className="overview-header">
<div className="overview-text">

2
docs/docs/cloud-ci-cd/github-integration.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# GitHub Deployment
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/cloud-ci-cd/index.mdx
View File

@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Continuous Integration and Continuous Deployment with Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/cloud-ci-cd/one-click-deploy/create-one-click-to-deploy-apps.mdx
View File

@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Create a One Click Deploy to Hasura Cloud App
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/cloud-ci-cd/one-click-deploy/index.mdx
View File

@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# One Click Deploy to Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/cloud-ci-cd/preview-apps.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Preview Apps
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## TL;DR

2
docs/docs/cloud-ci-cd/regression-tests.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Regression Tests on Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/data-federation/schema-registry.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Schema Registry
<ProductBadge standard free standard pro />
<ProductBadge free pro />
## Introduction

2
docs/docs/databases/database-config/cloud-connection-pooling.mdx
View File

@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Elastic Connection Pools
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/databases/database-config/data-connector-config.mdx
View File

@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Data Connector Config
<ProductBadge ce free standard pro ee self />
<ProductBadge ce free pro ee self />
## Introduction

2
docs/docs/databases/database-config/read-replicas.mdx
View File

@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Read Replicas
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

2
docs/docs/databases/mariadb/cloud.mdx
View File

@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Getting Started with MariaDB in Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/databases/mariadb/index.mdx
View File

@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# MariaDB
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
## Introduction

2
docs/docs/databases/mongodb/cloud.mdx
View File

@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Get Started with MongoDB in Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/databases/mongodb/index.mdx
View File

@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# MongoDB
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
## Introduction

2
docs/docs/databases/mysql/cloud.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Getting Started with MySQL in Hasura Cloud
<div className="badge-container">
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
</div>
## Introduction

283
docs/docs/databases/mysql/index.mdx
View File

@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# MySQL
<div className="badge-container">
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
</div>
## Introduction
@ -54,152 +54,157 @@ schema.
<div className="feature-matrix-tables">
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Remote Relationships</td>
<td>✅</td>
</tr>
<tr>
<td>Views</td>
<td>✅</td>
</tr>
<tr>
<td>Default Values</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Remote Relationships</td>
<td>✅</td>
</tr>
<tr>
<td>Views</td>
<td>✅</td>
</tr>
<tr>
<td>Default Values</td>
<td>✅</td>
</tr>
</table>
### Queries
### Queries
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Simple</td>
<td>✅</td>
</tr>
<tr>
<td>Nested Object</td>
<td>✅</td>
</tr>
<tr>
<td>Aggregation</td>
<td>✅</td>
</tr>
<tr>
<td>Filter / Search</td>
<td>✅</td>
</tr>
<tr>
<td>Sort</td>
<td>✅</td>
</tr>
<tr>
<td>Distinct</td>
<td>✅</td>
</tr>
<tr>
<td>Paginate</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Arguments</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Queries</td>
<td>✅</td>
</tr>
<tr>
<td>Variables / Aliases / Fragments</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Simple</td>
<td>✅</td>
</tr>
<tr>
<td>Nested Object</td>
<td>✅</td>
</tr>
<tr>
<td>Aggregation</td>
<td>✅</td>
</tr>
<tr>
<td>Filter / Search</td>
<td>✅</td>
</tr>
<tr>
<td>Sort</td>
<td>✅</td>
</tr>
<tr>
<td>Distinct</td>
<td>✅</td>
</tr>
<tr>
<td>Paginate</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Arguments</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Queries</td>
<td>✅</td>
</tr>
<tr>
<td>Variables / Aliases / Fragments</td>
<td>✅</td>
</tr>
</table>
### Mutations
### Mutations
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Insert</td>
<td>✅</td>
</tr>
<tr>
<td>Upsert</td>
<td>✅</td>
</tr>
<tr>
<td>Update</td>
<td>✅</td>
</tr>
<tr>
<td>Delete</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple per Request</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Insert</td>
<td>✅</td>
</tr>
<tr>
<td>Upsert</td>
<td>✅</td>
</tr>
<tr>
<td>Update</td>
<td>✅</td>
</tr>
<tr>
<td>Delete</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple per Request</td>
<td>✅</td>
</tr>
</table>
### Subscriptions
### Subscriptions
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Value of Field</td>
<td>❌</td>
</tr>
<tr>
<td>Updates to Rows</td>
<td>❌</td>
</tr>
<tr>
<td>Value of Derived Field</td>
<td>❌</td>
</tr>
<tr>
<td>Streaming Subscriptions</td>
<td>❌</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>Value of Field</td>
<td>❌</td>
</tr>
<tr>
<td>Updates to Rows</td>
<td>❌</td>
</tr>
<tr>
<td>Value of Derived Field</td>
<td>❌</td>
</tr>
<tr>
<td>Streaming Subscriptions</td>
<td>❌</td>
</tr>
</table>
### Event Triggers
### Event Triggers
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>INSERT</td>
<td>❌</td>
</tr>
<tr>
<td>UPDATE</td>
<td>❌</td>
</tr>
<tr>
<td>DELETE</td>
<td>❌</td>
</tr>
<tr>
<td>MANUAL</td>
<td>❌</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>MySQL</td>
</tr>
<tr>
<td>INSERT</td>
<td>❌</td>
</tr>
<tr>
<td>UPDATE</td>
<td>❌</td>
</tr>
<tr>
<td>DELETE</td>
<td>❌</td>
</tr>
<tr>
<td>MANUAL</td>
<td>❌</td>
</tr>
</table>
</div>

2
docs/docs/databases/oracle/cloud.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Getting Started with Oracle in Hasura Cloud
<div className="badge-container">
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
</div>
## Introduction

283
docs/docs/databases/oracle/index.mdx
View File

@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Oracle
<div className="badge-container">
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
</div>
## Introduction
@ -51,152 +51,157 @@ schema.
<div className="feature-matrix-tables">
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Remote Relationships</td>
<td>✅</td>
</tr>
<tr>
<td>Views</td>
<td>✅</td>
</tr>
<tr>
<td>Default Values</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Remote Relationships</td>
<td>✅</td>
</tr>
<tr>
<td>Views</td>
<td>✅</td>
</tr>
<tr>
<td>Default Values</td>
<td>✅</td>
</tr>
</table>
### Queries
### Queries
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Simple</td>
<td>✅</td>
</tr>
<tr>
<td>Nested Object</td>
<td>✅</td>
</tr>
<tr>
<td>Aggregation</td>
<td>✅</td>
</tr>
<tr>
<td>Filter / Search</td>
<td>✅</td>
</tr>
<tr>
<td>Sort</td>
<td>✅</td>
</tr>
<tr>
<td>Distinct</td>
<td>✅</td>
</tr>
<tr>
<td>Paginate</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Arguments</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Queries</td>
<td>✅</td>
</tr>
<tr>
<td>Variables / Aliases / Fragments</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Simple</td>
<td>✅</td>
</tr>
<tr>
<td>Nested Object</td>
<td>✅</td>
</tr>
<tr>
<td>Aggregation</td>
<td>✅</td>
</tr>
<tr>
<td>Filter / Search</td>
<td>✅</td>
</tr>
<tr>
<td>Sort</td>
<td>✅</td>
</tr>
<tr>
<td>Distinct</td>
<td>✅</td>
</tr>
<tr>
<td>Paginate</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Arguments</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple Queries</td>
<td>✅</td>
</tr>
<tr>
<td>Variables / Aliases / Fragments</td>
<td>✅</td>
</tr>
</table>
### Mutations
### Mutations
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Insert</td>
<td>✅</td>
</tr>
<tr>
<td>Upsert</td>
<td>✅</td>
</tr>
<tr>
<td>Update</td>
<td>✅</td>
</tr>
<tr>
<td>Delete</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple per Request</td>
<td>✅</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Insert</td>
<td>✅</td>
</tr>
<tr>
<td>Upsert</td>
<td>✅</td>
</tr>
<tr>
<td>Update</td>
<td>✅</td>
</tr>
<tr>
<td>Delete</td>
<td>✅</td>
</tr>
<tr>
<td>Multiple per Request</td>
<td>✅</td>
</tr>
</table>
### Subscriptions
### Subscriptions
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Value of Field</td>
<td>❌</td>
</tr>
<tr>
<td>Updates to Rows</td>
<td>❌</td>
</tr>
<tr>
<td>Value of Derived Field</td>
<td>❌</td>
</tr>
<tr>
<td>Streaming Subscriptions</td>
<td>❌</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>Value of Field</td>
<td>❌</td>
</tr>
<tr>
<td>Updates to Rows</td>
<td>❌</td>
</tr>
<tr>
<td>Value of Derived Field</td>
<td>❌</td>
</tr>
<tr>
<td>Streaming Subscriptions</td>
<td>❌</td>
</tr>
</table>
### Event Triggers
### Event Triggers
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>INSERT</td>
<td>❌</td>
</tr>
<tr>
<td>UPDATE</td>
<td>❌</td>
</tr>
<tr>
<td>DELETE</td>
<td>❌</td>
</tr>
<tr>
<td>MANUAL</td>
<td>❌</td>
</tr>
</table>
{' '}
<table>
<tr>
<td>Feature</td>
<td>Oracle</td>
</tr>
<tr>
<td>INSERT</td>
<td>❌</td>
</tr>
<tr>
<td>UPDATE</td>
<td>❌</td>
</tr>
<tr>
<td>DELETE</td>
<td>❌</td>
</tr>
<tr>
<td>MANUAL</td>
<td>❌</td>
</tr>
</table>
</div>

2
docs/docs/deployment/graphql-engine-flags/reference.mdx
View File

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

2
docs/docs/deployment/health-checks/source-health-check.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Source Health Check
<ProductBadge free standard ee self />
<ProductBadge free ee self />
## Introduction

2
docs/docs/getting-started/getting-started-cloud.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Quickstart with Hasura Cloud
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/account-management/billing/billing-owner.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Billing Owner
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/hasura-cloud/account-management/billing/credits.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Coupons and Credits
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/hasura-cloud/account-management/billing/index.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Billing
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/hasura-cloud/account-management/billing/payment-methods.mdx
View File

@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Manage Payment Methods
<ProductBadge standard pro />
<ProductBadge pro />
## Introduction

2
docs/docs/hasura-cloud/account-management/billing/receipts.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Receipts
<ProductBadge standard pro />
<ProductBadge pro />
## Introduction

2
docs/docs/hasura-cloud/account-management/email-change.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Change Email Address
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/account-management/index.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# <AccountManagement /> Account Management
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/domains.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Custom Domains
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

8
docs/docs/hasura-cloud/environments.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Manage Development Environments
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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

2
docs/docs/hasura-cloud/graphql-api-explorer.mdx
View File

@ -22,7 +22,7 @@ import Explorer from '@site/static/icons/features/graphql_api_explorer_2.svg';
# <Explorer /> Hasura GraphQL API Explorer
<ProductBadge ce free standard pro ee self />
<ProductBadge ce free pro ee self />
## TL;DR

2
docs/docs/hasura-cloud/heroku-url-sync.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Heroku Database Integration
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
:::info Note

2
docs/docs/hasura-cloud/high-availability.mdx
View File

@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# High-Availability Configuration
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/hasura-cloud/plans.mdx
View File

@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Plans and Pricing
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/collaborators.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Project Collaborators
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/create.mdx
View File

@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Create Projects
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/delete.mdx
View File

@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Delete Projects
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Overview

2
docs/docs/hasura-cloud/projects/details.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Project Details
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/env-vars.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Project Env Vars
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/hibernation.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Project Hibernation and Reactivation
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/index.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# <Collaborators /> Projects & Collaborators
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/maintenance-mode.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Maintenance Mode
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

13
docs/docs/hasura-cloud/projects/move-project-manual.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Transfer Existing Hasura Cloud Project to a New Project
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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.

2
docs/docs/hasura-cloud/projects/move-project-v2-manual.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Manually Move Hasura Cloud v1.3 Projects to Hasura v2.0
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/move-project-v2.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Updating Hasura Cloud v1.3 Projects to Hasura v2.0
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/ownership.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Transfer Project Ownership
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

6
docs/docs/hasura-cloud/projects/pricing.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Switch Pricing Plans
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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:
<Thumbnail src="/img/projects/upgrade-to-paid-plan.png" alt="Upgrade to the Standard plan" width="1200px" />
<Thumbnail src="/img/projects/upgrade-to-paid-plan.png" alt="Upgrade to the Professional plan" width="1200px" />
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:
<Thumbnail src="/img/projects/switch-to-free-plan.png" alt="Switch from Standard to Free tier" width="1200px" />
<Thumbnail src="/img/projects/switch-to-free-plan.png" alt="Switch from Professional to Free tier" width="1200px" />
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.

2
docs/docs/hasura-cloud/projects/recover.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Recover Project
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/regions.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Deployment Regions
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/hasura-cloud/projects/secure.mdx
View File

@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Secure Projects
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

8
docs/docs/hasura-cloud/regions.mdx
View File

@ -14,12 +14,13 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Regions
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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)

8
docs/docs/hasura-cloud/vercel-integration.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Vercel Integration
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## 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.

2
docs/docs/observability/cloud-monitoring/errors.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Errors
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
## Introduction

2
docs/docs/observability/cloud-monitoring/operations.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Operations
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud-monitoring/subscription-workers.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Subscription Workers
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud-monitoring/tracing.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Distributed Tracing
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud-monitoring/usage.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Usage Summaries
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud-monitoring/websockets.mdx
View File

@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Websockets
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Overview

2
docs/docs/observability/cloud/azure-monitor.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Azure Monitor Integration on Hasura Cloud
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud/datadog.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Datadog Integration on Hasura Cloud
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud/index.mdx
View File

@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Hasura Cloud observability integrations with external services
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud/newrelic.mdx
View File

@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# New Relic Integration on Hasura Cloud
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

2
docs/docs/observability/cloud/prometheus.mdx
View File

@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Prometheus Integration for Hasura Cloud
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction

3
docs/docs/observability/enterprise-edition/index.mdx
View File

@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Hasura EE observability integrations with external services
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## Introduction
@ -35,4 +35,3 @@ choice:
- [Prometheus](prometheus/index.mdx)
- [OpenTelemetry](/observability/opentelemetry.mdx)

2
docs/docs/observability/opentelemetry.mdx
View File

@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Export Traces and Metrics to OpenTelemetry Compliant Receiver from Hasura
<div className="badge-container">
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
<div className="badge badge-gray heading-badge">Beta</div>
</div>

6
docs/docs/observability/overview.mdx
View File

@ -17,7 +17,7 @@ import Observability from '@site/static/icons/features/observability.svg';
# <Observability /> Observability
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
<div className="overview-header">
<div className="overview-text">
@ -46,7 +46,9 @@ import Observability from '@site/static/icons/features/observability.svg';
<VersionedLink to="/observability/cloud-monitoring/index/">Hasura Cloud Built-in Monitoring</VersionedLink>
</li>
<li>
<VersionedLink to="/observability/enterprise-edition/prometheus/pre-built-dashboards">Pre-built dashboards with Hasura EE</VersionedLink>
<VersionedLink to="/observability/enterprise-edition/prometheus/pre-built-dashboards">
Pre-built dashboards with Hasura EE
</VersionedLink>
</li>
<li>
<VersionedLink to="/observability/db-observability/">Database observability</VersionedLink>

2
docs/docs/observability/query-tags.mdx
View File

@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Query Tags
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## Introduction

4
docs/docs/policies/sla.mdx
View File

@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Hasura Cloud Service Level Agreement (SLA)
<ProductBadge standard pro ee />
<ProductBadge pro ee />
## 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.

10
docs/docs/schema/bigquery/native-queries.mdx
View File

@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
# BigQuery: Native Queries
<div className="badge-container">
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
</div>
## What are Native Queries?
@ -319,8 +319,8 @@ Once the modal is open, fill in the forms with:
<TabItem value="cli" label="CLI">
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 {
</TabItem>
</Tabs>
## Relationships with tables
Relationships can be defined between tables and Native Queries residing in the same source.

6
docs/docs/schema/ms-sql-server/native-queries.mdx
View File

@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
# MS SQL Server: Native Queries
<div className="badge-container">
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
</div>
## What are Native Queries?
@ -325,8 +325,8 @@ Finally, add any optional fields that you would like to be included in the Logic
<TabItem value="cli" label="CLI">
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:

6
docs/docs/schema/ms-sql-server/stored-procedures.mdx
View File

@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
# MS SQL Server: Stored Procedures
<div className="badge-container">
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
</div>
## What are stored procedures?
@ -291,8 +291,8 @@ stored procedure.
</TabItem>
<TabItem value="cli" label="CLI">
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:

93
docs/docs/schema/postgres/input-validations.mdx
View File

@ -20,7 +20,7 @@ import TabItem from '@theme/TabItem';
# Postgres: Input Validations
<ProductBadge ce free standard pro ee self />
<ProductBadge ce free pro ee self />
## 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
</TabItem>
<TabItem value="api" label="API">
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.
</TabItem>
</Tabs>
:::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": "<version-integer>",
@ -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 `<model_name>_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
`<model_name>_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 `<model_name>_updates!` graphql type. If it is an update mutation by primary key, then it will
also contain the `<model_name>_pk_columns_input!`
structure of the `<model_name>_updates!` graphql type. If it is an update mutation by primary key, then it will also
contain the `<model_name>_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
`<model_name>_bool_exp!` graphql type. If it is a delete mutation by primary key, then it will also contain the
`<model_name>_pk_columns_input!`
`<model_name>_bool_exp!` graphql type. If it is a delete mutation by primary key, then it will also contain the
`<model_name>_pk_columns_input!`
### Response

15
docs/docs/schema/snowflake/native-queries.mdx
View File

@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
# Snowflake: Native Queries
<div className="badge-container">
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
</div>
## 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
<TabItem value="cli" label="CLI">
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:

4
docs/docs/security/allow-list.mdx
View File

@ -148,7 +148,7 @@ query ($id: Int!) {
## Role-based Allow List
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
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
<ProductBadge free standard pro ee />
<ProductBadge free pro ee />
### Hasura Cloud

10
docs/docs/security/api-limits.mdx
View File

@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# API Limits
<ProductBadge standard pro ee self />
<ProductBadge pro ee self />
## 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.
:::

2
docs/docs/security/container-images.mdx
View File

@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
# Proactive Vulnerability Scanning of Container Images
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
## Overview

4
docs/docs/security/disable-graphql-introspection.mdx
View File

@ -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
<ProductBadge free standard pro ee self />
<ProductBadge free pro ee self />
## Introduction

2
docs/docs/security/overview.mdx
View File

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

8
docs/src/components/ProductBadge/index.tsx
View File

@ -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) {
</VersionedLink>
);
}
if (props.standard) {
links.push(
<VersionedLink key="standard" to="/hasura-cloud/overview/#cloud-professional">
Cloud Standard
</VersionedLink>
);
}
if (props.pro) {
links.push(
<VersionedLink key="pro" to="/hasura-cloud/overview/#cloud-professional">

1
docs/wiki/style/product-badges.mdx
View File

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