Pydantic Settings v2 env preflight

Compare BaseSettings fields with env names before deploy.

Paste a settings class and env-name lines. This local checker reports missing required names, unknown env names, v2 import boundaries, and secret-like fields without copying values into the report.

Settings snippets

Names only

Settings class snippet.env names or lines

Do not paste real .env values, database URLs, API keys, tokens, or passwords. The report prints names only.

Settings result

fail

Required Pydantic settings names are missing from the pasted env-name list.

Fields4

Env names3

Missing1

Unknown1

fail

Missing required env names

APP_DATABASE_URL

warn

Unknown env names

APP_LEGACY_NAME

warn

Boundary to review

Some env names do not match detected settings fields.

warn

Boundary to review

Secret-like names were detected; keep values out of this page and copied reports.

Detected names

Expected env names

APP_DATABASE_URLAPP_ENVIRONMENTAPP_REDIS_URLAPP_WORKER_COUNT

Secret-like names

APP_DATABASE_URL

Safe report

Pydantic Settings v2 env preflight
Status: fail
Summary: Required Pydantic settings names are missing from the pasted env-name list.

Detected settings fields: database_url -> APP_DATABASE_URL (required), environment -> APP_ENVIRONMENT (required), redis_url -> APP_REDIS_URL (defaulted), worker_count -> APP_WORKER_COUNT (defaulted)
Provided env names: APP_ENVIRONMENT, APP_LEGACY_NAME, APP_WORKER_COUNT
Missing required env names: APP_DATABASE_URL
Unknown env names: APP_LEGACY_NAME
Secret-like names: APP_DATABASE_URL

Warnings:
- Some env names do not match detected settings fields.
- Secret-like names were detected; keep values out of this page and copied reports.

Checklist:
- Compare names only; keep .env values, database URLs, and tokens out of this page.
- Confirm BaseSettings is imported from pydantic-settings in v2 projects.
- Restart the process after changing env values because settings are often cached at import time.
- Run your own Settings() load test in the target environment before deploying.

Scope: static name check only. This report never includes .env values, tokens, database URLs, or runtime validation.