pydantic-prod-safety-validator-rejects-dev-defaults-at-boot
Without a production safety validator on the Settings model, dev secrets (default DB passwords, JWT secrets, Cube secrets) are silently accepted when RDASH_ENV=production. Added a model_validator that checks 7 dev-default scenarios and raises a single structured error at boot time. This pattern should be standard on every service that uses env-driven config.
Related
- 2026-04-04-oracle-001-self-architecture-analysis
- rdash-env-var-naming-drift-breaks-prod-boot
- module-level-env-reads-with-dev-fallback-bypass-runtime-conf
- openclaw
- docker
- env-var-naming-drift-causes-silent-prod-boot-with-dev-defaul
- module-level-env-reads-bypass-runtime-env-in-python
- pydantic-model-validator-prod-safety-gate-pattern
- makefile-awk-help-extractor-excludes-digit-containing-target
- python-module-level-env-read-bypasses-prod-safety
- pydantic-settings-prod-safety-validator-pattern
- pydantic-model-validator-prod-safety-gate
- dependabot-limit-zero-blocks-bumps-not-security