deployment-end-to-end

Type: decision

Decision

Each platform capability owns its code and deployment pipeline end-to-end, with no shared pipelines crossing capability boundaries.

Why

Without isolation, changing one capability can trigger or break another's functionality.

Violations

• Resource created or modified directly in Azure portal or CLI outside a Deployment Stack.
• Configuration value hardcoded in Bicep instead of injected from GitHub variables.

Links

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

← Back to knowledge graph