Centralized Configuration Management

What would you like to Propose?

Problem: Each module may have its own .env or application.properties, creating inconsistencies.

Feature Request: Implement a shared configuration module (e.g., via Spring Cloud Config or simple YAML config repo) that defines:

1. Common environment variables(DB URL, JWT secret, Vault key)
2. Per-service overrides

Benefit:
Easier maintenance and secure key rotation

Issue details

Problem: Each module may have its own .env or application.properties, creating inconsistencies.

Additional Information

I’d like to suggest moving away from maintaining separate .env or application.properties files for each microservice, which often leads to inconsistencies and makes configuration management more complex. Instead, adopting a centralized configuration system—such as Spring Cloud Config or a shared YAML-based repository—can help define common environment variables (like DB URLs, JWT secrets, Vault keys) in one place, while still allowing service-specific overrides. This approach not only simplifies maintenance and improves visibility, but also enhances security through easier key rotation and streamlines deployment for DevOps teams by making configuration access and updates more efficient.

No project files, tests, or entry points are named. First inspect whether this repository contains microservices or configuration files relevant to the proposal, then clarify whether Spring Cloud Config or a shared YAML repository is intended. Done requires an agreed architecture covering common variables, per-service overrides, and secure key rotation.