env-config-management

What problem does it solve?

Managing environment variables and Spring profiles across different environments (local, test, prod) can lead to inconsistencies, security vulnerabilities (hardcoded secrets), and deployment failures. Manual verification is error-prone and time-consuming, increasing the risk of production issues.

Core Features & Use Cases

• Secure Secret Management: Enforces strict separation of sensitive information into .env.local (gitignore'd), preventing accidental exposure.
• Fail-Fast Configuration: Prevents silent failures by disallowing default values in Spring profiles, ensuring missing variables cause immediate errors during startup.
• DRY Principle Enforcement: Guides against redundant overrides, promoting clean, concise, and maintainable configuration files.
• Use Case: Automatically review and update the application-prod.yml file to ensure all sensitive credentials are replaced with ${VAR_NAME} placeholders and no default values are present, then verify the corresponding .env.common file for consistency.

Quick Start

Review the application-local.yml file and ensure all sensitive information is replaced with environment variable placeholders, then check .env.local for the actual values.