Hasura
API gatewayhasura
GraphQL engine exposing a database as a permissioned GraphQL and REST API.
- Provider
- default
- Kind
- API gateway
- Category
- Edge
- Official docs
- https://hasura.io/docs/2.0/index/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| adminSecret | boolean | — | no | false | inherited |
| allowList | boolean | — | no | false | inherited |
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | ▸ none |
| concurrencyLimit | boolean | — | no | false | ▸ false |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| jwtAuth | boolean | — | no | false | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | ▸ http |
| rateLimiting | boolean | — | no | false | ▸ false |
| tls | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "hasura", component: "hasura" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAzure API Managementazure-api-managementAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalCloudflare Privacy Gatewaycloudflare-privacy-gatewayGeneric API gatewayapi-gatewayApache APISIXapisixApollo GraphOSapollo-graphosEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayGloo GatewayglooHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Hasura: GraphQL engine that exposes a database as a GraphQL and REST API with row-level # permissions. Per the Hasura documentation an engine started without an admin secret serves # requests as the admin role, and the allow-list is off until enabled. schemaVersion: "1" type: "component" id: "hasura" kind: "api-gateway" provider: "default" docs: "https://hasura.io/docs/2.0/index/" defaults: managed: false auth: "none" rateLimiting: false protocol: "http" concurrencyLimit: false properties: adminSecret: type: "boolean" default: false allowList: type: "boolean" default: false jwtAuth: type: "boolean" default: false