landing-zone-template

Type: regulative

Decision

Each landing zone must have its own parameter file and its own trigger workflow.

Why

A shared trigger means acting on one landing zone risks redeploying another team.

Violations

• Generated workflow name not matching the lz-* prefix, which breaks fan-out discovery.
• One parameter file covering more than one landing zone.

Anchor

no-human-touch

Implements

• landing-zone

Files

• landing-zones/managementGroup-AppName-environment.bicepparam
• .github/workflows/template-lz-template.yml
• .github/workflows/requestNew-Landing-Zone.yml

Links

• deployment-logic-reusable-workflow (depends-on) — Per landing zone triggers share centralized deployment logic through the reusable workflow.
• platform-azure-identity (depends-on) — The platform Azure identity's credentials are what let the template deploy landing zone resources.

← Back to knowledge graph