From a2acd3bffe9cd21a65baa18d275d3ccd6b83f8b7 Mon Sep 17 00:00:00 2001 From: Eldon Marks Date: Tue, 26 May 2026 09:51:42 -0400 Subject: [PATCH] fix(env): allowlist JVSPATIAL_POSTGRES_* keys The Postgres backend (jvspatial/db/factory.py, jvspatial/db/postgres.py) reads JVSPATIAL_POSTGRES_DSN, JVSPATIAL_POSTGRES_MIN_POOL_SIZE, JVSPATIAL_POSTGRES_MAX_POOL_SIZE, and JVSPATIAL_POSTGRES_POOLER_MODE, but the canonical ALLOWED_ENV_KEYS set in env_adapter.py was missing all four. PG deployments printed "Unknown JVSPATIAL_* env var ignored" at boot, and JVSPATIAL_STRICT_ENV_ALLOWLIST=true would have made them fatal. Co-Authored-By: Claude Opus 4.7 (1M context) --- jvspatial/env_adapter.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/jvspatial/env_adapter.py b/jvspatial/env_adapter.py index a89f492..7e6f64d 100644 --- a/jvspatial/env_adapter.py +++ b/jvspatial/env_adapter.py @@ -244,6 +244,10 @@ def server_config_overrides_from_env() -> Dict[str, Any]: "JVSPATIAL_MONGODB_DB_NAME", "JVSPATIAL_MONGODB_MAX_POOL_SIZE", "JVSPATIAL_MONGODB_MIN_POOL_SIZE", + "JVSPATIAL_POSTGRES_DSN", + "JVSPATIAL_POSTGRES_MIN_POOL_SIZE", + "JVSPATIAL_POSTGRES_MAX_POOL_SIZE", + "JVSPATIAL_POSTGRES_POOLER_MODE", "JVSPATIAL_DYNAMODB_TABLE_NAME", "JVSPATIAL_DYNAMODB_REGION", "JVSPATIAL_DYNAMODB_ENDPOINT_URL",