mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-08-15 13:40:29 +03:00
docs: remove standard cloud tier references throughout docs
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10254 GitOrigin-RevId: 84e28b38e1a10eeefe207acd207bc8b584eea20d
This commit is contained in:
parent
dcf5944aa5
commit
6d7865b383
@ -17,7 +17,7 @@ import Player from '@site/src/components/Player';
|
|||||||
|
|
||||||
# Import Action from OpenAPI Spec
|
# Import Action from OpenAPI Spec
|
||||||
|
|
||||||
<ProductBadge ce free standard pro ee self />
|
<ProductBadge ce free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
|
|||||||
|
|
||||||
# Hasura Cloud API Reference
|
# Hasura Cloud API Reference
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## 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`: `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`: `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`: `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. |
|
| under `projectOptions`: `envVars` | ENV vars to be set for the created Preview App. |
|
||||||
|
|
||||||
#### Output Fields
|
#### Output Fields
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Metadata API Reference: API Limits
|
# Metadata API Reference: API Limits
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -521,7 +521,7 @@ X-Hasura-Role: admin
|
|||||||
|
|
||||||
## cleanup_event_trigger_logs {#metadata-cleanup-event-trigger-logs}
|
## 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.
|
`cleanup_event_trigger_logs` is used to manually delete the event logs for a given Event Trigger.
|
||||||
|
|
||||||
|
@ -23,7 +23,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Metadata API Reference: Observability Options
|
# Metadata API Reference: Observability Options
|
||||||
|
|
||||||
<ProductBadge ce free standard pro ee self />
|
<ProductBadge ce free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
@ -31,7 +31,7 @@ The API to manage `Observability` related metadata configurations.
|
|||||||
|
|
||||||
## Logs and metrics configuration
|
## Logs and metrics configuration
|
||||||
|
|
||||||
<ProductBadge standard pro />
|
<ProductBadge pro />
|
||||||
|
|
||||||
These are the configurations that govern the metrics and logging output for debugging and analytics.
|
These are the configurations that govern the metrics and logging output for debugging and analytics.
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Source Health Check API Reference
|
# Source Health Check API Reference
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
description: Hasura Cloud and Hasura Enterprise multiple admin secrets
|
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:
|
keywords:
|
||||||
- hasura
|
- hasura
|
||||||
- docs
|
- docs
|
||||||
@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Multiple Admin Secrets
|
# Multiple Admin Secrets
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
description: Hasura Cloud and Hasura Enterprise multiple JWT Secrets
|
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:
|
keywords:
|
||||||
- hasura
|
- hasura
|
||||||
- docs
|
- docs
|
||||||
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Multiple JWT Secrets
|
# Multiple JWT Secrets
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -244,7 +244,7 @@ auth-webhook is made after the time specified in those fields and a new websocke
|
|||||||
|
|
||||||
## Webhook Auth Caching
|
## 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.
|
Session variables from a webhook token can be cached to improve the performance of the request.
|
||||||
|
|
||||||
|
@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Caching Config
|
# Caching Config
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Enable Caching in Hasura Enterprise Edition
|
# Enable Caching in Hasura Enterprise Edition
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import Caching from '@site/static/icons/features/caching.svg';
|
|||||||
|
|
||||||
# <Caching /> Hasura Caching
|
# <Caching /> Hasura Caching
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
<div className="overview-header">
|
<div className="overview-header">
|
||||||
<div className="overview-text">
|
<div className="overview-text">
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# GitHub Deployment
|
# GitHub Deployment
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Continuous Integration and Continuous Deployment with Hasura Cloud
|
# Continuous Integration and Continuous Deployment with Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Create a One Click Deploy to Hasura Cloud App
|
# Create a One Click Deploy to Hasura Cloud App
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# One Click Deploy to Hasura Cloud
|
# One Click Deploy to Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Preview Apps
|
# Preview Apps
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## TL;DR
|
## TL;DR
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Regression Tests on Hasura Cloud
|
# Regression Tests on Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Schema Registry
|
# Schema Registry
|
||||||
|
|
||||||
<ProductBadge standard free standard pro />
|
<ProductBadge free pro />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Elastic Connection Pools
|
# Elastic Connection Pools
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Data Connector Config
|
# Data Connector Config
|
||||||
|
|
||||||
<ProductBadge ce free standard pro ee self />
|
<ProductBadge ce free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Read Replicas
|
# Read Replicas
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Getting Started with MariaDB in Hasura Cloud
|
# Getting Started with MariaDB in Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# MariaDB
|
# MariaDB
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Get Started with MongoDB in Hasura Cloud
|
# Get Started with MongoDB in Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# MongoDB
|
# MongoDB
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
# Getting Started with MySQL in Hasura Cloud
|
# Getting Started with MySQL in Hasura Cloud
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
# MySQL
|
# MySQL
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
@ -54,152 +54,157 @@ schema.
|
|||||||
|
|
||||||
<div className="feature-matrix-tables">
|
<div className="feature-matrix-tables">
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>MySQL</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>MySQL</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Remote Relationships</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Remote Relationships</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Views</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Views</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Default Values</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Default Values</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Queries
|
### Queries
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>MySQL</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>MySQL</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Simple</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Simple</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Nested Object</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Nested Object</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Aggregation</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Aggregation</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Filter / Search</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Filter / Search</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Sort</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Sort</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Distinct</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Distinct</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Paginate</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Paginate</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple Arguments</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple Arguments</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple Queries</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple Queries</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Variables / Aliases / Fragments</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Variables / Aliases / Fragments</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Mutations
|
### Mutations
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>MySQL</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>MySQL</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Insert</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Insert</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Upsert</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Upsert</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Update</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Update</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Delete</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Delete</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple per Request</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple per Request</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Subscriptions
|
### Subscriptions
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>MySQL</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>MySQL</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Value of Field</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Value of Field</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Updates to Rows</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Updates to Rows</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Value of Derived Field</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Value of Derived Field</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Streaming Subscriptions</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Streaming Subscriptions</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Event Triggers
|
### Event Triggers
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>MySQL</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>MySQL</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>INSERT</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>INSERT</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>UPDATE</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>UPDATE</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>DELETE</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>DELETE</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>MANUAL</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>MANUAL</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
# Getting Started with Oracle in Hasura Cloud
|
# Getting Started with Oracle in Hasura Cloud
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
@ -13,7 +13,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
# Oracle
|
# Oracle
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
@ -51,152 +51,157 @@ schema.
|
|||||||
|
|
||||||
<div className="feature-matrix-tables">
|
<div className="feature-matrix-tables">
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>Oracle</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>Oracle</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Remote Relationships</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Remote Relationships</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Views</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Views</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Default Values</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Default Values</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Queries
|
### Queries
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>Oracle</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>Oracle</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Simple</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Simple</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Nested Object</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Nested Object</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Aggregation</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Aggregation</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Filter / Search</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Filter / Search</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Sort</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Sort</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Distinct</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Distinct</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Paginate</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Paginate</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple Arguments</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple Arguments</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple Queries</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple Queries</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Variables / Aliases / Fragments</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Variables / Aliases / Fragments</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Mutations
|
### Mutations
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>Oracle</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>Oracle</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Insert</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Insert</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Upsert</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Upsert</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Update</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Update</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Delete</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Delete</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Multiple per Request</td>
|
<tr>
|
||||||
<td>✅</td>
|
<td>Multiple per Request</td>
|
||||||
</tr>
|
<td>✅</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Subscriptions
|
### Subscriptions
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>Oracle</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>Oracle</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Value of Field</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Value of Field</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Updates to Rows</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Updates to Rows</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Value of Derived Field</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Value of Derived Field</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>Streaming Subscriptions</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>Streaming Subscriptions</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
### Event Triggers
|
### Event Triggers
|
||||||
|
|
||||||
<table>
|
{' '}
|
||||||
<tr>
|
<table>
|
||||||
<td>Feature</td>
|
<tr>
|
||||||
<td>Oracle</td>
|
<td>Feature</td>
|
||||||
</tr>
|
<td>Oracle</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>INSERT</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>INSERT</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>UPDATE</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>UPDATE</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>DELETE</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>DELETE</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
<tr>
|
</tr>
|
||||||
<td>MANUAL</td>
|
<tr>
|
||||||
<td>❌</td>
|
<td>MANUAL</td>
|
||||||
</tr>
|
<td>❌</td>
|
||||||
</table>
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
@ -645,7 +645,7 @@ The [maximum cache size](/caching/enterprise-caching.mdx), measured in MB, for q
|
|||||||
| **Env var** | `HASURA_GRAPHQL_MAX_CACHE_SIZE` |
|
| **Env var** | `HASURA_GRAPHQL_MAX_CACHE_SIZE` |
|
||||||
| **Accepted values** | Integer (Representing cache size measured in MB) |
|
| **Accepted values** | Integer (Representing cache size measured in MB) |
|
||||||
| **Default** | `1` |
|
| **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
|
### Metadata Database Extension Schema
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Source Health Check
|
# Source Health Check
|
||||||
|
|
||||||
<ProductBadge free standard ee self />
|
<ProductBadge free ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Quickstart with Hasura Cloud
|
# Quickstart with Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Billing Owner
|
# Billing Owner
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Coupons and Credits
|
# Coupons and Credits
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Billing
|
# Billing
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Manage Payment Methods
|
# Manage Payment Methods
|
||||||
|
|
||||||
<ProductBadge standard pro />
|
<ProductBadge pro />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Receipts
|
# Receipts
|
||||||
|
|
||||||
<ProductBadge standard pro />
|
<ProductBadge pro />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Change Email Address
|
# Change Email Address
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# <AccountManagement /> Account Management
|
# <AccountManagement /> Account Management
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Custom Domains
|
# Custom Domains
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Manage Development Environments
|
# Manage Development Environments
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## 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
|
### 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
|
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
|
[GitHub deployment](/cloud-ci-cd/github-integration.mdx) feature. But before we do that, we need to setup Metadata &
|
||||||
Metadata & Migrations of your local setup that you can apply to your Cloud project. For a lowdown on Hasura Metadata &
|
Migrations of your local setup that you can apply to your Cloud project. For a lowdown on Hasura Metadata & Migrations
|
||||||
Migrations refer the guide [here](/migrations-metadata-seeds/overview.mdx)
|
refer the guide [here](/migrations-metadata-seeds/overview.mdx)
|
||||||
|
|
||||||
### Step 1: Install Hasura CLI
|
### Step 1: Install Hasura CLI
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ import Explorer from '@site/static/icons/features/graphql_api_explorer_2.svg';
|
|||||||
|
|
||||||
# <Explorer /> Hasura GraphQL API Explorer
|
# <Explorer /> Hasura GraphQL API Explorer
|
||||||
|
|
||||||
<ProductBadge ce free standard pro ee self />
|
<ProductBadge ce free pro ee self />
|
||||||
|
|
||||||
## TL;DR
|
## TL;DR
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Heroku Database Integration
|
# Heroku Database Integration
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
:::info Note
|
:::info Note
|
||||||
|
|
||||||
|
@ -12,7 +12,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# High-Availability Configuration
|
# High-Availability Configuration
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Plans and Pricing
|
# Plans and Pricing
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Project Collaborators
|
# Project Collaborators
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Create Projects
|
# Create Projects
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Delete Projects
|
# Delete Projects
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Project Details
|
# Project Details
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Project Env Vars
|
# Project Env Vars
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Project Hibernation and Reactivation
|
# Project Hibernation and Reactivation
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# <Collaborators /> Projects & Collaborators
|
# <Collaborators /> Projects & Collaborators
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Maintenance Mode
|
# Maintenance Mode
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Transfer Existing Hasura Cloud Project to a New Project
|
# Transfer Existing Hasura Cloud Project to a New Project
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## 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
|
- You can [rename](/hasura-cloud/projects/details.mdx#rename-project) your new project to the same name as the earlier
|
||||||
project if you wish.
|
project if you wish.
|
||||||
|
|
||||||
- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/domains.mdx) for your
|
- If you haven't renamed your new project or set up a [custom domain](/hasura-cloud/domains.mdx) for your project, you
|
||||||
project, you might want to update any clients consuming the GraphQL API to point to the new project's GraphQL
|
might want to update any clients consuming the GraphQL API to point to the new project's GraphQL endpoint.
|
||||||
endpoint.
|
|
||||||
|
|
||||||
## Zero-downtime transfer
|
## Zero-downtime transfer
|
||||||
|
|
||||||
To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/domains.mdx)
|
To achieve a zero-downtime transfer, you will need to have a [custom domain](/hasura-cloud/domains.mdx) attached to your
|
||||||
attached to your Cloud project. Once the new project is set up identically as the old one, you can update the DNS
|
Cloud project. Once the new project is set up identically as the old one, you can update the DNS entries for your custom
|
||||||
entries for your custom domain to the new project to have a seamless transfer of traffic to the new project.
|
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
|
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.
|
[rename](/hasura-cloud/projects/details.mdx#rename-project) your new project with the same name as the earlier project.
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Manually Move Hasura Cloud v1.3 Projects to Hasura v2.0
|
# Manually Move Hasura Cloud v1.3 Projects to Hasura v2.0
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Updating Hasura Cloud v1.3 Projects to Hasura v2.0
|
# Updating Hasura Cloud v1.3 Projects to Hasura v2.0
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Transfer Project Ownership
|
# Transfer Project Ownership
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Switch Pricing Plans
|
# Switch Pricing Plans
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
Hasura has different pricing plans that you can choose from based on your requirements. This page explains how to switch
|
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:
|
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.
|
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:
|
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
|
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.
|
be on the `Free` tier. If the `Free` tier limit is exhausted, the project might become inactive.
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Recover Project
|
# Recover Project
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Deployment Regions
|
# Deployment Regions
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -15,7 +15,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Secure Projects
|
# Secure Projects
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -14,12 +14,13 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Regions
|
# Regions
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
Hasura Cloud is available in multiple regions on both Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure Cloud. This
|
Hasura Cloud is available in multiple regions on both Amazon Web Services (AWS), Google Cloud Platform (GCP) and
|
||||||
allows you to choose the region that is closest to your users to reduce latency and improve performance.
|
Microsoft Azure Cloud. This allows you to choose the region that is closest to your users to reduce latency and improve
|
||||||
|
performance.
|
||||||
|
|
||||||
## Supported regions
|
## Supported regions
|
||||||
|
|
||||||
@ -47,7 +48,6 @@ allows you to choose the region that is closest to your users to reduce latency
|
|||||||
- Frankfurt, Germany
|
- Frankfurt, Germany
|
||||||
- St. Ghislain, Belgium
|
- St. Ghislain, Belgium
|
||||||
|
|
||||||
|
|
||||||
### Azure Cloud (Azure)
|
### Azure Cloud (Azure)
|
||||||
|
|
||||||
- US East (Virginia)
|
- US East (Virginia)
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Vercel Integration
|
# Vercel Integration
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
@ -155,9 +155,9 @@ Your integration will only be successfully configured upon clicking the `Install
|
|||||||
|
|
||||||
:::info Note
|
:::info Note
|
||||||
|
|
||||||
- If a [custom domain](/hasura-cloud/domains.mdx) is added to the Hasura Cloud project, you'll have to set this
|
- If a [custom domain](/hasura-cloud/domains.mdx) is added to the Hasura Cloud project, you'll have to set this custom
|
||||||
custom value to `HASURA_PROJECT_ENDPOINT` and `NEXT_HASURA_PROJECT_ENDPOINT` manually in the respective Vercel
|
value to `HASURA_PROJECT_ENDPOINT` and `NEXT_HASURA_PROJECT_ENDPOINT` manually in the respective Vercel project's
|
||||||
project's settings.
|
settings.
|
||||||
- Similarly if the Hasura Cloud project's admin secret is changed, you will have to edit the `HASURA_ADMIN_SECRET`
|
- 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.
|
manually in the respective Vercel project's settings.
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Errors
|
# Errors
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Operations
|
# Operations
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Subscription Workers
|
# Subscription Workers
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Distributed Tracing
|
# Distributed Tracing
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Usage Summaries
|
# Usage Summaries
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -16,7 +16,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Websockets
|
# Websockets
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Azure Monitor Integration on Hasura Cloud
|
# Azure Monitor Integration on Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Datadog Integration on Hasura Cloud
|
# Datadog Integration on Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Hasura Cloud observability integrations with external services
|
# Hasura Cloud observability integrations with external services
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# New Relic Integration on Hasura Cloud
|
# New Relic Integration on Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -20,7 +20,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Prometheus Integration for Hasura Cloud
|
# Prometheus Integration for Hasura Cloud
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Hasura EE observability integrations with external services
|
# Hasura EE observability integrations with external services
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
@ -35,4 +35,3 @@ choice:
|
|||||||
|
|
||||||
- [Prometheus](prometheus/index.mdx)
|
- [Prometheus](prometheus/index.mdx)
|
||||||
- [OpenTelemetry](/observability/opentelemetry.mdx)
|
- [OpenTelemetry](/observability/opentelemetry.mdx)
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
# Export Traces and Metrics to OpenTelemetry Compliant Receiver from Hasura
|
# Export Traces and Metrics to OpenTelemetry Compliant Receiver from Hasura
|
||||||
|
|
||||||
<div className="badge-container">
|
<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 className="badge badge-gray heading-badge">Beta</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ import Observability from '@site/static/icons/features/observability.svg';
|
|||||||
|
|
||||||
# <Observability /> Observability
|
# <Observability /> Observability
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
<div className="overview-header">
|
<div className="overview-header">
|
||||||
<div className="overview-text">
|
<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>
|
<VersionedLink to="/observability/cloud-monitoring/index/">Hasura Cloud Built-in Monitoring</VersionedLink>
|
||||||
</li>
|
</li>
|
||||||
<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>
|
||||||
<li>
|
<li>
|
||||||
<VersionedLink to="/observability/db-observability/">Database observability</VersionedLink>
|
<VersionedLink to="/observability/db-observability/">Database observability</VersionedLink>
|
||||||
|
@ -17,7 +17,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Query Tags
|
# Query Tags
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -14,7 +14,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Hasura Cloud Service Level Agreement (SLA)
|
# Hasura Cloud Service Level Agreement (SLA)
|
||||||
|
|
||||||
<ProductBadge standard pro ee />
|
<ProductBadge pro ee />
|
||||||
|
|
||||||
## Introduction
|
## 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
|
We calculate SLA uptime monthly and measure uptime with an HTTP request to the `/v1/version` endpoint on a project at a
|
||||||
regular interval.
|
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
|
[terms of service](https://hasura.io/legal/hasura-cloud-terms-of-service/). Cloud Enterprise users should reference
|
||||||
their contracts for details.
|
their contracts for details.
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
|
|||||||
# BigQuery: Native Queries
|
# BigQuery: Native Queries
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## What are Native Queries?
|
## What are Native Queries?
|
||||||
@ -319,8 +319,8 @@ Once the modal is open, fill in the forms with:
|
|||||||
|
|
||||||
<TabItem value="cli" label="CLI">
|
<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`
|
You can create a logical model by adding it to the appropriate database definition in the
|
||||||
file:
|
`metadata > databases > databases.yaml` file:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
logical_models:
|
logical_models:
|
||||||
@ -519,8 +519,7 @@ A future release will allow mutations to be specified using Native Queries.
|
|||||||
## Permissions
|
## Permissions
|
||||||
|
|
||||||
Native queries will inherit the permissions of the Logical Model that they return. See the
|
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
|
[documentation on Logical Models](/schema/bigquery/logical-models.mdx) for an explanation of how to add permissions.
|
||||||
permissions.
|
|
||||||
|
|
||||||
## Relationships
|
## Relationships
|
||||||
|
|
||||||
@ -679,7 +678,6 @@ query {
|
|||||||
</TabItem>
|
</TabItem>
|
||||||
</Tabs>
|
</Tabs>
|
||||||
|
|
||||||
|
|
||||||
## Relationships with tables
|
## Relationships with tables
|
||||||
|
|
||||||
Relationships can be defined between tables and Native Queries residing in the same source.
|
Relationships can be defined between tables and Native Queries residing in the same source.
|
||||||
|
@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
|
|||||||
# MS SQL Server: Native Queries
|
# MS SQL Server: Native Queries
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## What are 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
|
|||||||
|
|
||||||
<TabItem value="cli" label="CLI">
|
<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`
|
You can create a logical model by adding it to the appropriate database definition in the
|
||||||
file:
|
`metadata > databases > databases.yaml` file:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
logical_models:
|
logical_models:
|
||||||
|
@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
|
|||||||
# MS SQL Server: Stored Procedures
|
# MS SQL Server: Stored Procedures
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## What are stored procedures?
|
## What are stored procedures?
|
||||||
@ -291,8 +291,8 @@ stored procedure.
|
|||||||
</TabItem>
|
</TabItem>
|
||||||
<TabItem value="cli" label="CLI">
|
<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`
|
You can create a logical model by adding it to the appropriate database definition in the
|
||||||
file:
|
`metadata > databases > databases.yaml` file:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
logical_models:
|
logical_models:
|
||||||
|
@ -20,7 +20,7 @@ import TabItem from '@theme/TabItem';
|
|||||||
|
|
||||||
# Postgres: Input Validations
|
# Postgres: Input Validations
|
||||||
|
|
||||||
<ProductBadge ce free standard pro ee self />
|
<ProductBadge ce free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## 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
|
Many times, we need to perform validations on the input arguments of a GraphQL mutation before inserting, deleting or
|
||||||
or updating the data.
|
updating the data.
|
||||||
|
|
||||||
Hasura provides a way to add input validations to your GraphQL mutations which route the input arguments of a
|
Hasura provides a way to add input validations to your GraphQL mutations which route the input arguments of a GraphQL
|
||||||
GraphQL mutation to an HTTP webhook to perform complex validation logic.
|
mutation to an HTTP webhook to perform complex validation logic.
|
||||||
|
|
||||||
### Example
|
### Example
|
||||||
|
|
||||||
@ -42,19 +42,20 @@ Consider you have the following GraphQL mutation:
|
|||||||
|
|
||||||
```graphql
|
```graphql
|
||||||
mutation insert_users {
|
mutation insert_users {
|
||||||
insert_users(objects: [{name: "John", phone: "999"}]) {
|
insert_users(objects: [{ name: "John", phone: "999" }]) {
|
||||||
affected_rows
|
affected_rows
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
mutation update_users {
|
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
|
affected_rows
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
You can define the input validations for the above mutations to perform the following checks:
|
You can define the input validations for the above mutations to perform the following checks:
|
||||||
|
|
||||||
1. Check that the `name` field is not empty
|
1. Check that the `name` field is not empty
|
||||||
2. Check that the `phone` field is a valid phone number
|
2. Check that the `phone` field is a valid phone number
|
||||||
3. Check that the `email` field is a valid email address
|
3. Check that the `email` field is a valid email address
|
||||||
@ -94,11 +95,10 @@ file, eg:
|
|||||||
definition:
|
definition:
|
||||||
url: http://www.somedomain.com/validateProducts
|
url: http://www.somedomain.com/validateProducts
|
||||||
headers:
|
headers:
|
||||||
- name: X-Validate-Input-API-Key
|
- name: X-Validate-Input-API-Key
|
||||||
value_from_env: VALIDATION_HOOK_API_KEY
|
value_from_env: VALIDATION_HOOK_API_KEY
|
||||||
forward_client_headers: true
|
forward_client_headers: true
|
||||||
timeout: 5
|
timeout: 5
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
Apply the Metadata by running:
|
Apply the Metadata by running:
|
||||||
@ -110,8 +110,8 @@ hasura metadata apply
|
|||||||
</TabItem>
|
</TabItem>
|
||||||
<TabItem value="api" label="API">
|
<TabItem value="api" label="API">
|
||||||
|
|
||||||
You can define the input validations when using the [permissions Metadata API](/api-reference/metadata-api/permission.mdx).
|
You can define the input validations when using the
|
||||||
Example with a Postgres DB:
|
[permissions Metadata API](/api-reference/metadata-api/permission.mdx). Example with a Postgres DB:
|
||||||
|
|
||||||
```http {14-21}
|
```http {14-21}
|
||||||
POST /v1/metadata HTTP/1.1
|
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 `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.
|
The `definition` field provides the necessary context for communicating and submitting the data for input validation. It
|
||||||
It is an object with the following fields.
|
is an object with the following fields.
|
||||||
- `url` - *Required*, a [string value](https://hasura.io/docs/latest/api-reference/syntax-defs/#webhookurl) which
|
|
||||||
|
- `url` - _Required_, a [string value](https://hasura.io/docs/latest/api-reference/syntax-defs/#webhookurl) which
|
||||||
supports templating environment variables.
|
supports templating environment variables.
|
||||||
- `headers` - *Optional*, a list of headers to be sent to the URL.
|
- `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
|
- `forward_client_headers` - _Optional_, default is `false`. If set to `true` the client headers are forwarded to the
|
||||||
the URL.
|
URL.
|
||||||
- `timeout` - *Optional*, default is `10`. The number of seconds to wait for a response before timing out.
|
- `timeout` - _Optional_, default is `10`. The number of seconds to wait for a response before timing out.
|
||||||
|
|
||||||
</TabItem>
|
</TabItem>
|
||||||
</Tabs>
|
</Tabs>
|
||||||
|
|
||||||
:::caution Reduced performance
|
:::caution Reduced performance
|
||||||
|
|
||||||
Mutations that involve input validation **may exhibit slower performance** compared to mutations without
|
Mutations that involve input validation **may exhibit slower performance** compared to mutations without validation. The
|
||||||
validation. The execution time of the webhook URL can become a bottleneck, potentially reaching the maximum limit
|
execution time of the webhook URL can become a bottleneck, potentially reaching the maximum limit specified by the
|
||||||
specified by the `timeout` configuration value, the default of which is 10 seconds.
|
`timeout` configuration value, the default of which is 10 seconds.
|
||||||
|
|
||||||
:::
|
:::
|
||||||
|
|
||||||
## How it works
|
## How it works
|
||||||
|
|
||||||
Following are the steps that are performed by mutations types (`insert/update/delete`)
|
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:
|
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)
|
nested inserts)
|
||||||
2. If there is a `validate_input` permission defined on a table, then any mutation arguments targeting that table are
|
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.
|
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
|
3. If all handlers validate the mutation arguments, then the request proceeds. **A transaction with the database will
|
||||||
the database will only be started after the validation is completed and successful.**
|
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
|
4. If any webhook rejects the mutation data, then the request is aborted. An `error` message from the URL can also be
|
||||||
be forwarded to the client.
|
forwarded to the client.
|
||||||
|
|
||||||
Consider the following sample mutation:
|
Consider the following sample mutation:
|
||||||
|
|
||||||
```graphql
|
```graphql
|
||||||
mutation insertAuthorWithArticles($name: String, $email:String, $articles_content:[article_insert_input!]!) {
|
mutation insertAuthorWithArticles($name: String, $email: String, $articles_content: [article_insert_input!]!) {
|
||||||
insert_author(objects: {name: $name, email: $email, articles: {data: $articles_content}}){
|
insert_author(objects: { name: $name, email: $email, articles: { data: $articles_content } }) {
|
||||||
returning {
|
returning {
|
||||||
first_name
|
first_name
|
||||||
articles {
|
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
|
The above mutation targets the `author` and `article` tables, involving a nested insert of an article into the author
|
||||||
author model. Assuming that the `validate_input` permission is defined for both tables, the validation process
|
model. Assuming that the `validate_input` permission is defined for both tables, the validation process unfolds as
|
||||||
unfolds as follows:
|
follows:
|
||||||
|
|
||||||
1. The validation webhook specified for the `author` table is contacted first, including the inserted row with
|
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.
|
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
|
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.
|
rows into the respective tables.
|
||||||
|
|
||||||
|
|
||||||
## Webhook specification per mutation type
|
## Webhook specification per mutation type
|
||||||
|
|
||||||
### Request
|
### Request
|
||||||
|
|
||||||
When a mutation on a table with `validate_input` configuration is executed, before making a database
|
When a mutation on a table with `validate_input` configuration is executed, before making a database transaction, Hasura
|
||||||
transaction, Hasura sends the mutation argument data to the validation HTTP webhook using a `POST` request.
|
sends the mutation argument data to the validation HTTP webhook using a `POST` request.
|
||||||
|
|
||||||
The request payload is of the format:
|
The request payload is of the format:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
"version": "<version-integer>",
|
"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.
|
- `role`: Hasura session role on which permissions are enforced.
|
||||||
- `session_variables`: Session variables that aid in enforcing permissions. Session variable names always starts with
|
- `session_variables`: Session variables that aid in enforcing permissions. Session variable names always starts with
|
||||||
`x-hasura-*`.
|
`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.
|
- `data.input`: List of rows to be inserted which are specified in the `objects` input field of insert mutation. Also
|
||||||
Also includes nested data of relationships. The structure of this field will be similar to the JSONified structure
|
includes nested data of relationships. The structure of this field will be similar to the JSONified structure of the
|
||||||
of the `<model_name>_insert_input!` graphql type.
|
`<model_name>_insert_input!` graphql type.
|
||||||
|
|
||||||
Note that, in `data.input`, if the data to be inserted contains nested inserts, then:
|
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
|
- `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
|
structure of the `<model_name>_updates!` graphql type. If it is an update mutation by primary key, then it will also
|
||||||
also contain the `<model_name>_pk_columns_input!`
|
contain the `<model_name>_pk_columns_input!`
|
||||||
|
|
||||||
#### Delete Mutations
|
#### 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
|
- `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>_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>_pk_columns_input!`
|
||||||
|
|
||||||
### Response
|
### Response
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import Thumbnail from '@site/src/components/Thumbnail';
|
|||||||
# Snowflake: Native Queries
|
# Snowflake: Native Queries
|
||||||
|
|
||||||
<div className="badge-container">
|
<div className="badge-container">
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
## What are Native Queries?
|
## What are Native Queries?
|
||||||
@ -208,8 +208,8 @@ native_queries:
|
|||||||
max_length:
|
max_length:
|
||||||
type: integer
|
type: integer
|
||||||
code:
|
code:
|
||||||
SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) < {{max_length}} THEN ''
|
SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) <
|
||||||
else '...' END)) AS "excerpt", date as "date" FROM article
|
{{max_length}} THEN '' else '...' END)) AS "excerpt", date as "date" FROM article
|
||||||
returns: article_excerpt
|
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
|
:::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
|
```sql
|
||||||
SELECT id as "id", title as "title", (substring(content, 1, {{max_length}}) || (CASE WHEN length(content) < {{max_length}} THEN ''
|
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
|
else '...' END)) AS "excerpt", date as "date" FROM article
|
||||||
```
|
```
|
||||||
|
|
||||||
Notice that each field that we are returning we provide the `as "field"`.
|
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">
|
<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`
|
You can create a logical model by adding it to the appropriate database definition in the
|
||||||
file:
|
`metadata > databases > databases.yaml` file:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
logical_models:
|
logical_models:
|
||||||
|
@ -148,7 +148,7 @@ query ($id: Int!) {
|
|||||||
|
|
||||||
## Role-based Allow List
|
## 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.
|
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
|
## Quick-create allowed operations
|
||||||
|
|
||||||
<ProductBadge free standard pro ee />
|
<ProductBadge free pro ee />
|
||||||
|
|
||||||
### Hasura Cloud
|
### Hasura Cloud
|
||||||
|
|
||||||
|
@ -19,7 +19,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# API Limits
|
# API Limits
|
||||||
|
|
||||||
<ProductBadge standard pro ee self />
|
<ProductBadge pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
@ -53,8 +53,8 @@ be used to rate-limit requests.
|
|||||||
|
|
||||||
To enable rate limiting on Hasura Enterprise, you must set the
|
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
|
[`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
|
variable or the [`--rate-limit-redis-url`](/deployment/graphql-engine-flags/reference.mdx#rate-limit-redis-url) server
|
||||||
with the appropriate Redis connection string.
|
flag with the appropriate Redis connection string.
|
||||||
|
|
||||||
:::
|
:::
|
||||||
|
|
||||||
@ -153,8 +153,8 @@ sources.
|
|||||||
|
|
||||||
:::info Time limits on Hasura Cloud projects
|
:::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
|
All Free tier and Professional tier Hasura Cloud projects get a time limit of 60 seconds. When the cloud limit is hit,
|
||||||
error contains the code `tenant-time-limit-exceeded` in the error message.
|
the error contains the code `tenant-time-limit-exceeded` in the error message.
|
||||||
|
|
||||||
:::
|
:::
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Proactive Vulnerability Scanning of Container Images
|
# Proactive Vulnerability Scanning of Container Images
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
description: Hasura Cloud and Enterprise Edition disable GraphQL introspection
|
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:
|
keywords:
|
||||||
- hasura
|
- hasura
|
||||||
- docs
|
- docs
|
||||||
@ -21,7 +21,7 @@ import ProductBadge from '@site/src/components/ProductBadge';
|
|||||||
|
|
||||||
# Disable GraphQL Introspection
|
# Disable GraphQL Introspection
|
||||||
|
|
||||||
<ProductBadge free standard pro ee self />
|
<ProductBadge free pro ee self />
|
||||||
|
|
||||||
## Introduction
|
## Introduction
|
||||||
|
|
||||||
|
@ -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'
|
title: 'Cloud & Enterprise Edition: API Security'
|
||||||
keywords:
|
keywords:
|
||||||
- hasura
|
- hasura
|
||||||
|
@ -5,7 +5,6 @@ import VersionedLink from '@site/src/components/VersionedLink';
|
|||||||
type ProductBadgeProps = {
|
type ProductBadgeProps = {
|
||||||
ce: boolean;
|
ce: boolean;
|
||||||
free: boolean;
|
free: boolean;
|
||||||
standard: boolean;
|
|
||||||
pro: boolean;
|
pro: boolean;
|
||||||
ee: boolean;
|
ee: boolean;
|
||||||
self: boolean;
|
self: boolean;
|
||||||
@ -28,13 +27,6 @@ function createLinks(props: ProductBadgeProps) {
|
|||||||
</VersionedLink>
|
</VersionedLink>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
if (props.standard) {
|
|
||||||
links.push(
|
|
||||||
<VersionedLink key="standard" to="/hasura-cloud/overview/#cloud-professional">
|
|
||||||
Cloud Standard
|
|
||||||
</VersionedLink>
|
|
||||||
);
|
|
||||||
}
|
|
||||||
if (props.pro) {
|
if (props.pro) {
|
||||||
links.push(
|
links.push(
|
||||||
<VersionedLink key="pro" to="/hasura-cloud/overview/#cloud-professional">
|
<VersionedLink key="pro" to="/hasura-cloud/overview/#cloud-professional">
|
||||||
|
@ -24,7 +24,6 @@ order of the props doesn't matter, but the props themselves are:
|
|||||||
| ---------- | ------------------------ |
|
| ---------- | ------------------------ |
|
||||||
| `ce` | Community Edition |
|
| `ce` | Community Edition |
|
||||||
| `free` | Cloud Free |
|
| `free` | Cloud Free |
|
||||||
| `standard` | Cloud Standard |
|
|
||||||
| `pro` | Cloud Professional |
|
| `pro` | Cloud Professional |
|
||||||
| `ee` | Cloud Enterprise Edition |
|
| `ee` | Cloud Enterprise Edition |
|
||||||
| `self` | Self-Hosted EE |
|
| `self` | Self-Hosted EE |
|
||||||
|
Loading…
Reference in New Issue
Block a user