config-lives-in-the-repo

Type: decision

Decision

Configuration has one committed source of truth — a single JSON file in the repo. Values are propagated to GitHub variables and Bicep parameters at deployment time. Nothing is set manually in the UI or injected out of band.

Why

Without one committed source, environments drift. Onboarding a new engineer means tracing values through the GitHub UI instead of reading a file.

Links

• landing-zone-application-profile — New repos receive a subset of platform variables at creation.
• platform-identity-azure — Per-environment client IDs sourced from this file.
• initial-setup — githubVariables.json must be committed with initial platform config values before BigBang first runs.

← Back to all decisions