deployment-config-in-repo

Type: decision

Decision

Repo-specific configuration is driven through GitHub variables — no value is set manually.

Why

GitHub environments are destroyed and recreated during BigBang — without variables committed to the repo, the platform state cannot be reproduced.

Violations

• Bicep parameter with hardcoded tenant ID or location instead of readEnvironmentVariable().
• GitHub variable created in UI.

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 knowledge graph