Skip to content

Commit 4b6d039

Browse files
authored
pull base content,head:MicrosoftDocs:main,into:wwlpublishsync
2 parents 5ba374c + f855ab4 commit 4b6d039

22 files changed

+298
-133
lines changed
491 KB
Loading

learn-pr/achievements/get-started-lakehouses.svg

Lines changed: 215 additions & 0 deletions
Loading

learn-pr/azure/arm-template-whatif/1-introduction.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
description: Introduction
99
author: mumian
1010
ms.author: jgao
11-
ms.date: 01/31/2025
11+
ms.date: 03/18/2025
1212
ms.topic: unit
1313
ms.custom:
1414
- team=nextgen

learn-pr/azure/arm-template-whatif/2-deployment-modes.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
description: Learn about the two deployment modes for Azure, incremental and complete.
99
author: mumian
1010
ms.author: jgao
11-
ms.date: 01/31/2025
11+
ms.date: 03/18/2025
1212
ms.topic: unit
1313
ms.custom:
1414
- team=nextgen

learn-pr/azure/arm-template-whatif/3-what-if.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ metadata:
55
adobe-target: true
66
prefetch-feature-rollout: true
77
title: Predict what a deployment will do by using what-if
8-
description: Deploying and hoping for the best is not the approach you should be taking. The what-if operation is here to address this fact. This unit will cover what it is and how to use it.
8+
description: Deploying and hoping for the best isn't the approach you should be taking. The what-if operation is here to address this fact. This unit covers what the operation is and how to use it.
99
author: mumian
1010
ms.author: jgao
11-
ms.date: 01/31/2025
11+
ms.date: 03/18/2025
1212
ms.topic: unit
1313
ms.custom:
1414
- team=nextgen

learn-pr/azure/arm-template-whatif/4-exercise-what-if.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
description: Use the what-if tool to predict what a deployment will carry out if it's applied.
99
author: mumian
1010
ms.author: jgao
11-
ms.date: 01/31/2025
11+
ms.date: 03/18/2025
1212
ms.topic: unit
1313
ms.custom: team=nextgen, devx-track-bicep
1414
zone_pivot_groups: arm-template-language-azure-shell-interface

learn-pr/azure/arm-template-whatif/5-knowledge-check.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
prefetch-feature-rollout: true
77
title: Knowledge check
88
description: Three multiple-choice questions
9-
ms.date: 01/31/2025
9+
ms.date: 03/18/2025
1010
author: mumian
1111
ms.author: jgao
1212
ms.topic: unit

learn-pr/azure/arm-template-whatif/6-summary.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ metadata:
66
prefetch-feature-rollout: true
77
title: Summary
88
description: Summary
9-
ms.date: 01/31/2025
9+
ms.date: 03/18/2025
1010
author: mumian
1111
ms.author: jgao
1212
ms.topic: unit

learn-pr/azure/arm-template-whatif/includes/4-exercise-what-if.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,8 @@ You start with an existing template that your team has been using. The template
3131

3232
1. Create a new file called *azuredeploy.json*.
3333

34-
1. Save the empty file so that Visual Studio Code loads the ARM template tooling.
35-
34+
1. Save the empty file so that Visual Studio Code loads the ARM template tooling.
35+
3636
You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you've saved the file. For example, you might want to create a *scripts* folder to save it in.
3737

3838
1. Copy the following code into *azuredeploy.json*.
@@ -49,8 +49,8 @@ You start with an existing template that your team has been using. The template
4949

5050
1. Create a new file called *main.bicep*.
5151

52-
1. Save the empty file so that Visual Studio Code loads the Bicep tooling.
53-
52+
1. Save the empty file so that Visual Studio Code loads the Bicep tooling.
53+
5454
You can either select **File** > **Save As** or select <kbd>Ctrl+S</kbd> in Windows (<kbd>⌘+S</kbd> on macOS). Be sure to remember where you've saved the file. For example, you might want to create a *scripts* folder to save it in.
5555

5656
1. Copy the following code into *main.bicep*.
@@ -173,7 +173,7 @@ To validate that your deployment has been created and sent to Azure, go to the [
173173

174174
::: zone pivot="jsonpowershell,jsoncli"
175175

176-
1. In the *azuredeploy.json* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
176+
1. In the *azuredeploy.json* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
177177

178178
:::code language="json" source="code/4-template-after.json" range="12-14" :::
179179

@@ -191,7 +191,7 @@ To validate that your deployment has been created and sent to Azure, go to the [
191191

192192
::: zone pivot="biceppowershell,bicepcli"
193193

194-
1. In the *main.bicep* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
194+
1. In the *main.bicep* file in Visual Studio Code, delete the tag named `Owner` and its value. After you're done, the `tags` property of the virtual network should look like this:
195195

196196
:::code language="bicep" source="code/4-template-after.bicep" range="6-8" :::
197197

@@ -273,9 +273,9 @@ The what-if output is similar to the following one:
273273

274274
Notice that the result is color-coded in addition to having a prefix:
275275

276-
- Purple and **~** for any modifications
277-
- Green and **+** for new resources to be created
278-
- Orange and **-** for deletions
276+
* Purple and **~** for any modifications
277+
* Green and **+** for new resources to be created
278+
* Orange and **-** for deletions
279279

280280
## Remove the resources in the template
281281

learn-pr/azure/arm-template-whatif/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
description: Apply the what-if command to see the effect of a deployment before it's applied.
88
ms.service: azure-resource-manager
99
manager: jasongroce
10-
ms.date: 01/31/2025
10+
ms.date: 03/18/2025
1111
author: mumian
1212
ms.author: jgao
1313
ms.topic: module

0 commit comments

Comments
 (0)