deployment-declarative-lifecycle

Type: decision

Decision

Within a deployment stack, what is not declared in code is deleted on the next deployment.

Why

Without this, resources removed from the stack's code persist in Azure — the code stops being the source of truth.

Violations

• Deployment Stack configured with detachAll removed resources persist with no cleanup path.
• Resources created directly in Azure are not managed by the Deployment Stack.

Links

• platform-test-environment — 'deleteAll' in test verifies code produces the expected Azure state before promotion to prod.
• landing-zone-lifecycle — A subscription is guaranteed empty after deleteAll, which makes subscription reuse safe.
• azure-native-services-only — Only ARM-native resources are stack-managed — azure-native-services-only is the prerequisite for deleteAll lifecycle enforcement.

← Back to knowledge graph