Environment variable reference

LeapView configuration is process-global. Environment settings apply to the entire instance and cannot be overridden per project resource. Values marked secret must come from the deployment environment or a secret manager.

Run leapview config validate to validate the active environment, or add --production to apply production requirements when LEAPVIEW_PRODUCTION is not set. Validation never prints configured values or secrets.

Administration

Agent

Analytics

Assets

Authentication

Bootstrap

Ci

Client

Connection

Connections

Delivery

Deployment

Development

Ducklake Retention

Jobs

Managed Data

Object Store

Operations

Postgres

Recovery

Refresh

Release

Security

Server

Site

Storage

Workload

Relationships

• production-dev-bypass: Production cannot bypass authentication. Failure: production serve must not enable LEAPVIEW_DEV_AUTH_BYPASS.
• production-oidc-complete: OIDC settings are all-or-none in production. Failure: production OIDC auth requires LEAPVIEW_OIDC_ISSUER_URL, LEAPVIEW_OIDC_CLIENT_ID, LEAPVIEW_OIDC_CLIENT_SECRET, and LEAPVIEW_OIDC_CALLBACK_URL.
• production-azure-complete: Azure settings are all-or-none in production. Failure: production Azure auth requires LEAPVIEW_AZURE_CLIENT_ID, LEAPVIEW_AZURE_CLIENT_SECRET, and LEAPVIEW_AZURE_CALLBACK_URL.
• production-auth-mode: Production requires local, API-token-only, OIDC, or Azure authentication. Failure: production serve requires OIDC auth env vars, Azure auth env vars, LEAPVIEW_LOCAL_AUTH, or LEAPVIEW_API_TOKEN_ONLY_AUTH.
• csrf-key: A CSRF key must contain at least 32 characters. Failure: serve requires LEAPVIEW_CSRF_KEY with at least 32 characters.
• production-metrics-token: Production requires a metrics bearer token with at least 32 characters. Failure: production metrics scraping requires LEAPVIEW_METRICS_BEARER_TOKEN with at least 32 characters.
• production-public-url: Production requires a canonical public URL. Failure: production serve requires LEAPVIEW_PUBLIC_URL.
• production-public-url-https: The production public URL must be an HTTPS origin without a path, query, fragment, or credentials. Failure: production serve requires LEAPVIEW_PUBLIC_URL to be an https origin.
• production-mcp-oauth-issuer-https: An external production MCP OAuth issuer must use HTTPS. Failure: production serve requires LEAPVIEW_MCP_OAUTH_ISSUER_URL to be an https URL.
• production-allowed-host: Production derives an allowed host from its public URL, explicit hosts, or a browser-auth callback host. Failure: production serve requires LEAPVIEW_PUBLIC_URL, LEAPVIEW_ALLOWED_HOSTS, or an OIDC/Azure callback URL host.
• production-secure-cookie: Production browser authentication requires secure cookies unless API-token-only mode is also enabled. Failure: production browser auth requires LEAPVIEW_COOKIE_SECURE=true.
• production-oidc-issuer-https: The production OIDC issuer must use HTTPS. Failure: production serve requires LEAPVIEW_OIDC_ISSUER_URL to be an https URL.
• production-oidc-callback-https: The production OIDC callback must use HTTPS. Failure: production serve requires LEAPVIEW_OIDC_CALLBACK_URL to be an https URL.
• production-oidc-provider-slug: The OIDC provider identifier must be route-safe. Failure: LEAPVIEW_OIDC_PROVIDER_ID must be a route-safe slug containing only letters, numbers, dots, underscores, or dashes.
• production-azure-callback-https: The production Azure callback must use HTTPS. Failure: production serve requires LEAPVIEW_AZURE_CALLBACK_URL to be an https URL.
• infisical-complete: The read-only Infisical target resolver is configured as one complete tuple. Failure: Infisical resolution requires LEAPVIEW_INFISICAL_BASE_URL, LEAPVIEW_INFISICAL_UNIVERSAL_CLIENT_ID, LEAPVIEW_INFISICAL_UNIVERSAL_CLIENT_SECRET, and LEAPVIEW_INFISICAL_ALLOWED_SCOPES.
• infisical-https: The Infisical backend is an HTTPS origin. Failure: LEAPVIEW_INFISICAL_BASE_URL must be an https origin.
• production-scim-token: A configured production SCIM token must contain at least 32 characters. Failure: production SCIM provisioning requires LEAPVIEW_SCIM_BEARER_TOKEN with at least 32 characters.
• managed-data-backend: Managed data uses a supported storage backend. Failure: LEAPVIEW_MANAGED_DATA_BACKEND must be local or s3.
• managed-data-runtime-dir: Every managed-data backend requires a private local runtime and staging directory. Failure: managed-data storage requires LEAPVIEW_MANAGED_DATA_DIR.
• managed-data-s3-location: The S3 managed-data backend requires a bucket and region. Failure: S3 managed-data storage requires LEAPVIEW_MANAGED_DATA_S3_BUCKET and LEAPVIEW_MANAGED_DATA_S3_REGION.
• production-managed-data-s3-endpoint: Production custom managed-data S3 endpoints must use encrypted transport. Failure: production managed-data S3 custom endpoints must use HTTPS.
• production-managed-data-s3-observation-profile: Production managed-data S3 writes require an explicit provider observation profile. Failure: production managed-data S3 requires LEAPVIEW_MANAGED_DATA_S3_OBSERVATION_ACCOUNT and LEAPVIEW_MANAGED_DATA_S3_OBSERVATION_PROFILE_ID.
• managed-data-s3-credentials: Managed-data S3 credentials are either omitted or configured as a complete key pair. Failure: managed-data S3 credentials require both LEAPVIEW_MANAGED_DATA_S3_ACCESS_KEY_ID and LEAPVIEW_MANAGED_DATA_S3_SECRET_ACCESS_KEY; a session token also requires that pair.
• managed-data-positive-limits: Managed-data upload, session, garbage-collection, and free-space limits are positive. Failure: managed-data limits, durations, and free-space thresholds must be positive.
• ducklake-retention-positive-limits: DuckLake catalog retention interval and file grace period are positive. Failure: production DuckLake retention interval and file grace period must be positive.
• managed-data-revision-limit: The managed-data revision limit is at least the per-file limit. Failure: LEAPVIEW_MANAGED_DATA_MAX_REVISION_BYTES must be at least LEAPVIEW_MANAGED_DATA_MAX_FILE_BYTES.
• object-store-backend: Immutable project sources and serving artifacts use a supported object-store backend. Failure: LEAPVIEW_OBJECT_STORE_BACKEND must be filesystem or s3.
• object-store-s3-location: The immutable S3 object store requires a bucket and region. Failure: S3 object storage requires LEAPVIEW_OBJECT_STORE_S3_BUCKET and LEAPVIEW_OBJECT_STORE_S3_REGION.
• production-object-store-s3-endpoint: Production custom immutable-object S3 endpoints must use encrypted transport. Failure: production object-store S3 custom endpoints must use HTTPS.
• object-store-s3-credentials: Immutable object-store S3 credentials are omitted for ambient AWS credentials or configured as a complete static pair. Failure: S3 object-store credentials require both LEAPVIEW_OBJECT_STORE_S3_ACCESS_KEY_ID and LEAPVIEW_OBJECT_STORE_S3_SECRET_ACCESS_KEY; a session token also requires that pair.
• object-store-s3-encryption-mode: Immutable object-store S3 encryption is explicit and supported. Failure: LEAPVIEW_OBJECT_STORE_S3_ENCRYPTION_MODE must be AES256 (SSE-S3), aws:kms (SSE-KMS), or sse-c (SSE-C).
• object-store-s3-sse-s3-keys: SSE-S3 does not accept encryption key identities. Failure: SSE-S3 object storage must not set encryption key references, provider keys, or customer keys.
• object-store-s3-sse-kms-keys: SSE-KMS requires both opaque and resolved provider key identities and no customer key. Failure: SSE-KMS object storage requires an opaque key reference and resolved provider key, and must not set a customer key.
• object-store-s3-sse-c-keys: SSE-C requires an opaque key epoch and customer key without a provider key. Failure: SSE-C object storage requires LEAPVIEW_OBJECT_STORE_S3_ENCRYPTION_KEY_REF and LEAPVIEW_OBJECT_STORE_S3_ENCRYPTION_CUSTOMER_KEY, and must not set a provider key.
• object-store-s3-sse-c-endpoint: A configured SSE-C custom endpoint must use HTTPS; the AWS default endpoint is also supported. Failure: SSE-C object storage custom endpoints must use HTTPS.