end-to-end-deployment

Type: decision

Decision

Each platform concern (policy, access control, management groups) owns its Bicep and workflows end-to-end.

Why

Without isolation, changing one concern can trigger or break another's deployment.

Links

• declarative-resource-lifecycle — deleteAll on each capability's stack ensures no orphaned resources after a declaration is removed.
• branch-gated-environment-promotion — Main branch is protected by branch policies.
• config-lives-in-the-repo — Capability configuration is sourced from the repo.
• platform-test-environment — Each platform capability deploys to the test hierarchy before production.

← Back to all decisions