envdrift 3.4.0

Prevent environment variable drift with Pydantic schema validation, pre-commit hooks, and dotenvx encryption

envdrift

Prevent environment variable drift between dev, staging, and production.

The Problem

• A missing DATABASE_URL in production causes a 3am outage
• Staging has NEW_FEATURE_FLAG=true but production doesn't
• "It works on my machine!" becomes your team's motto

The Solution

# Validate .env against Pydantic schema
envdrift validate .env --schema config.settings:Settings

# Compare dev vs prod
envdrift diff .env.development .env.production

# Check encryption status
envdrift encrypt .env.production --check

Installation

pip install envdrift

Quick Start

Define your schema:

from pydantic import Field
from pydantic_settings import BaseSettings, SettingsConfigDict

class Settings(BaseSettings):
    model_config = SettingsConfigDict(extra="forbid")

    DATABASE_URL: str = Field(json_schema_extra={"sensitive": True})
    API_KEY: str = Field(json_schema_extra={"sensitive": True})
    DEBUG: bool = False

Validate:

envdrift validate .env --schema config.settings:Settings

Features

Feature	envdrift
Schema validation	Pydantic-based
Cross-env diff	Yes
Pre-commit hooks	Yes
Encryption (dotenvx)	Yes
Vault integration	Azure, AWS, HashiCorp
CI/CD mode	Yes

Documentation

Full documentation: jainal09.github.io/envdrift

Development

git clone https://github.com/jainal09/envdrift.git
cd envdrift
make dev
make test
make docs-serve

License

MIT