Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
@@ -43,6 +43,8 @@ These keys are required for normal production application runtime unless the dep
|
||||
| `API_ACCESS_TOKEN` | Web/API runtime | Service-token boundary for internal and API operator calls. | Key name and redacted validator code only. |
|
||||
| `JWT_SECRET` | API runtime | API session JWT signing and verification boundary. | Key name and redacted validator code only. |
|
||||
| `ANALYTICS_TOKEN` | API runtime | Analytics ingestion and public analytics API token boundary. | Key name and redacted validator code only. |
|
||||
| `MCP_RESOURCE_URL` | MCP connector runtime | Public origin of the MCP resource server; used for RFC 9728 protected-resource metadata and OAuth audience binding. | Key name and host-normalization status only. |
|
||||
| `MCP_AUTHORIZATION_SERVER_URL` | Web/MCP runtime | Public origin of the OAuth authorization server (the web app) that issues MCP access tokens. | Key name and host-normalization status only. |
|
||||
|
||||
`DIRECT_URL` is database-owned and may be required by Prisma or deployment-specific migration workflows. Treat it as secret material whenever present, and document only whether the key is configured for the workflow being run.
|
||||
|
||||
@@ -61,9 +63,13 @@ Optional integration keys are feature-gated. Missing optional keys should produc
|
||||
| `MAILJET_FROM_NAME` | Mail provider boundary | A display name is needed for outbound mail. | Key name and configured/unconfigured status. |
|
||||
| `MAILJET_SECRET_KEY` | Mail provider boundary | Outbound Mailjet delivery is enabled (Basic-Auth password paired with the public key). | Key name and redacted validator code only. |
|
||||
| `MAILJET_WEBHOOK_SECRET` | Mail webhook boundary | Inbound Mailjet webhook Basic-Auth verification is enabled. | Key name and credential verification code only. |
|
||||
| `STRIPE_SK` | Billing and portal boundary | Stripe billing, subscriptions, or portal integrations are enabled. | Key name, mode label, and redacted validator code only. |
|
||||
| `STRIPE_WEBHOOK_SIGNING_SECRET` | Billing webhook boundary | Stripe webhook ingestion is enabled. | Key name and signature verification code only. |
|
||||
| `STRIPE_ACCOUNT_COUNTRY` | Billing boundary | Stripe billing is enabled under a deployment-region policy. | Expected country label and confirmation status only. |
|
||||
| `LAGO_API_URL` | Billing provider boundary | Lago billing sync is enabled. | Key name and redacted URL validation code only. |
|
||||
| `LAGO_API_KEY` | Billing provider boundary | Lago billing sync is enabled. | Key name and redacted validator code only. |
|
||||
| `LAGO_WEBHOOK_SECRET` | Billing webhook boundary | Lago webhook ingestion is enabled. | Key name and signature verification code only. |
|
||||
| `LAGO_TIMEOUT_MS` | Billing provider boundary | Lago billing sync uses a non-default timeout. | Timeout parse status only. |
|
||||
| `MOLLIE_API_KEY` | Payment provider boundary | Mollie payment checkout or webhook refetch is enabled. | Key name, mode label, and redacted validator code only. |
|
||||
| `MOLLIE_PROFILE_ID` | Payment provider boundary | Mollie payment creation requires an explicit website profile. | Key name and configured/unconfigured status. |
|
||||
| `MOLLIE_TIMEOUT_MS` | Payment provider boundary | Mollie payment gateway uses a non-default timeout. | Timeout parse status only. |
|
||||
| `PORTAL_SERVER_URL` | Portal/site-builder boundary | Portal server integration is enabled. | Key name, present/missing status, and redacted URL validation code only. |
|
||||
| `PORTAL_SERVER_FLY_TOKEN` | Portal automation boundary | Portal server automation is enabled. | Key name and redacted validator code only. |
|
||||
| `IMPORT_QUEUE_ENABLED` | Web enqueue and worker runtime | Import jobs should be sent through BullMQ. | Boolean enablement status and diagnostic code. |
|
||||
@@ -131,9 +137,7 @@ Diagnostics may say that a required Mailjet key is missing, a sender domain is n
|
||||
|
||||
`AI_PROCESSING_REGION` must match the approved deployment-region policy when AI generation is enabled. The cataloged AI provider keys currently include Mistral, Scaleway, and Aleph Alpha entries; deployment records must define the allowed provider order and region labels before production traffic is routed. `SCALEWAY_REGION` and `SCALEWAY_BASE_URL` are provider-specific markers and must match the deployment record.
|
||||
|
||||
`STRIPE_ACCOUNT_COUNTRY` must match the billing account country approved for the deployment. Do not use this key to create or mutate Stripe account configuration at runtime; it is an operator-visible guardrail for deployment review and drift detection.
|
||||
|
||||
`STRIPE_SK` and `STRIPE_WEBHOOK_SIGNING_SECRET` are active runtime secrets. Keep them in secret stores only; never paste Stripe keys, webhook signing secrets, event payloads, or customer identifiers into docs or verification records.
|
||||
`LAGO_API_URL`, `LAGO_API_KEY`, and `LAGO_WEBHOOK_SECRET` are the AD-27 billing-engine keys. `MOLLIE_API_KEY` and `MOLLIE_PROFILE_ID` are the payment-processor keys. Keep Lago and Mollie production values separate from staging/testmode values, and never paste provider keys, webhook secrets, payment references, invoice payloads, tenant identifiers, or customer identifiers into docs or verification records.
|
||||
|
||||
## Portal provider key group
|
||||
|
||||
|
||||
Reference in new issue
Block a user