Configuration Repository

Configuration for the example service is kept in a dedicated repository, separate from application source code. This keeps environment-specific values out of the application codebase and lets configuration changes go through their own review process.

The repository holds per-environment values such as instance sizing, feature flags, and connection settings. Nothing in the repository contains credentials directly; secrets are referenced by name and resolved at deploy time from a secret store.

Changes to the configuration repository are reviewed the same way as application code changes, and a change history is kept for every environment so that a previous configuration can always be restored.