Skip to content

Commit 0166d1a

Browse files
committed
clarify conditional deployment
1 parent 3cbdec1 commit 0166d1a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-resource-manager/bicep/conditional-resource-deployment.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: mumian
66
ms.author: jgao
77
ms.topic: conceptual
88
ms.custom: devx-track-bicep
9-
ms.date: 05/12/2023
9+
ms.date: 09/26/2023
1010
---
1111

1212
# Conditional deployment in Bicep
@@ -20,9 +20,9 @@ Sometimes you need to optionally deploy a resource or module in Bicep. Use the `
2020

2121
If you would rather learn about conditions through step-by-step guidance, see [Build flexible Bicep templates by using conditions and loops](/training/modules/build-flexible-bicep-templates-conditions-loops/).
2222

23-
## Deploy condition
23+
## Define condition for deployment
2424

25-
You can pass in a parameter value that indicates whether a resource is deployed. The following example conditionally deploys a DNS zone.
25+
In Bicep, you can conditionally deploy a resource by passing in a parameter that specifies whether the resource is deployed. You test the condition with an `if` statement in the resource declaration. The following example shows a Bicep file that conditionally deploys a DNS zone. When `deployZone` is `true`, it deploys the DNS zone. When `deployZone` is `false`, it skips deploying the DNS zone.
2626

2727
```bicep
2828
param deployZone bool

0 commit comments

Comments
 (0)