azure-policy-single-region

Type: regulative

Decision

Gazelle's single region must be sourced from GitHub variables.

Why

Without a committed variable, the regional boundary can drift between environments or be changed outside the repository.

Violations

• Single region hardcoded in the policy template instead of read from a GitHub variable.

Anchor

no-human-touch

Implements

• single-region

Files

• githubVariables.json
• .github/workflows/template-Azure-Policy.yml
• platform-management/policy/bicep/oases.bicep

Links

• deployment-config-in-repo (depends-on) — The single region relies on committed deployment configuration so BigBang can reproduce the same regional boundary.

← Back to knowledge graph