Skip to content

Commit 635fe22

Browse files
committed
use deployment stacks instead of complete mode
1 parent 9dece89 commit 635fe22

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

articles/azure-resource-manager/bicep/migrate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ In the _test_ phase of migrating your resources to Bicep, the goal is to verify
8080

8181
The test phase consists of two steps, which you complete in sequence:
8282

83-
1. **Run the ARM template deployment what-if operation.** To help you verify your converted templates before deployment, you can use the [Azure Resource Manager template deployment what-if operation](../templates/deploy-what-if.md). It compares the current state of your environment with the desired state that is defined in the template. The tool outputs the list of changes that will occur *without* applying the changes to your environment. You can use what-if with both incremental and complete mode deployments. Even if you plan to deploy your template using incremental mode, it's a good idea to run your what-if operation in complete mode.
83+
1. **Run the ARM template deployment what-if operation.** To help you verify your converted templates before deployment, you can use the [Azure Resource Manager template deployment what-if operation](../templates/deploy-what-if.md). It compares the current state of your environment with the desired state that is defined in the template. The tool outputs the list of changes that will occur *without* applying the changes to your environment. You can use what-if with both incremental and [complete mode](../templates/deployment-modes.md) deployments. Even if you plan to deploy your template using incremental mode, it's a good idea to run your what-if operation in complete mode.
8484

8585
1. **Perform a test deployment.** Before introducing your converted Bicep template to production, consider running multiple test deployments. If you have multiple environments (for example, development, test, and production), you may want to try deploying your template to one of your non-production environments first. After the deployment, compare the original resources with the new resource deployments for consistency.
8686

articles/azure-resource-manager/templates/deployment-modes.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,16 @@ title: Deployment modes
33
description: Describes how to specify whether to use a complete or incremental deployment mode with Azure Resource Manager.
44
ms.topic: conceptual
55
ms.custom: devx-track-arm-template
6-
ms.date: 03/20/2024
6+
ms.date: 12/11/2024
77
---
88

99
# Azure Resource Manager deployment modes
1010

1111
When deploying your resources, you specify that the deployment is either an incremental update or a complete update. The difference between these two modes is how Resource Manager handles existing resources in the resource group that aren't in the template.
1212

13+
> [!IMPORTANT]
14+
> Use [deployment stacks](../bicep/deployment-stacks.md) to perform resource deletions when using ARM templates or Bicep files, as the [complete mode](#complete-mode) will be gradually deprecated.
15+
1316
For both modes, Resource Manager tries to create all resources specified in the template. If the resource already exists in the resource group and its settings are unchanged, no operation is taken for that resource. If you change the property values for a resource, the resource is updated with those new values. If you try to update the location or type of an existing resource, the deployment fails with an error. Instead, deploy a new resource with the location or type that you need.
1417

1518
The default mode is incremental.

0 commit comments

Comments
 (0)