Skip to content

Commit 8ab82ff

Browse files
committed
incorporate feedback
1 parent 2761378 commit 8ab82ff

File tree

2 files changed

+39
-8
lines changed

2 files changed

+39
-8
lines changed
-9 Bytes
Loading

articles/azure-resource-manager/bicep/visual-studio-code.md

Lines changed: 39 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create Bicep files with Visual Studio Code
33
description: Learn how to use Visual Studio Code to create Bicep files.
44
ms.topic: how-to
5-
ms.date: 01/10/2025
5+
ms.date: 03/21/2025
66
ms.custom: devx-track-bicep
77
---
88

@@ -250,15 +250,17 @@ The Deployment Pane is a UI panel that lets you connect to your Azure subscripti
250250
To use deployment pane:
251251

252252
1. Open a `.bicep` or `.bicepparam` file in VS Code.
253-
1. Select the show deployment pane button on the upper right corner as shown in the following screenshot:
253+
1. There are two ways to open the deployment pane
254254

255-
:::image type="content" source="./media/visual-studio-code/visual-studio-code-open-deployment-pane.png" alt-text="Sceenshot of the open deployment pane button.":::
255+
- Select the show deployment pane button on the upper right corner as shown in the following screenshot:
256+
257+
:::image type="content" source="./media/visual-studio-code/visual-studio-code-open-deployment-pane.png" alt-text="Sceenshot of the open deployment pane button.":::
256258

257-
By default, VS Code opens the deployment pane on the side. To open it in a new tab, hold <kbd>Alt</kbd> while selecting the button.
259+
By default, VS Code opens the deployment pane on the side. To open it in a new tab, hold <kbd>Alt</kbd> while selecting the button.
258260

259-
Another way to open the deployment pane is through the command palette. Press <kbd>Ctrl</kdb>+<kbd>Shift</kbd>+<kbd>P</kbd>, then select either **Show Deployment Pane** or **Show Deployment Pane to the Side**.
261+
- Another way to open the deployment pane is through the command palette. Press <kbd>Ctrl</kdb>+<kbd>Shift</kbd>+<kbd>P</kbd>, then select either **Show Deployment Pane** or **Show Deployment Pane to the Side**.
260262

261-
:::image type="content" source="./media/visual-studio-code/visual-studio-code-show-deployment-pane.png" alt-text="Sceenshot of show deployment pane in command palette.":::
263+
:::image type="content" source="./media/visual-studio-code/visual-studio-code-show-deployment-pane.png" alt-text="Sceenshot of show deployment pane in command palette.":::
262264

263265
The following screenshot shows a successful deployment with the Bicep file validation results.
264266

@@ -269,8 +271,37 @@ To use deployment pane:
269271
1. Select your desired action - **Deploy**, **Validate**, or **What-if**.
270272

271273
- **Deploy**: deploys to Azure, and the result including the defined output are shown in the deployment pane.
272-
- **Validate**: verifies that all declared variables and parameters are used, ensures no sensitive information is returned, and detects any hard-coded values. In the preceding screenshot, the validation was successful.
273-
- **What-if**: executes a **What-If** analysis directly from the deployment pane. This performs the same function as that in Azure PowerShell and Azure CLI. The pane displays the results, showing any planned changes.
274+
- **Validate**: performs a live validation of the Bicep file against Azure, ensuring that the resources, parameters, and policies are correct in the actual deployment environment. Unlike a linter, which only checks for syntax errors, this validation interacts with Azure to detect potential deployment issues. It is equivalent to the validate command in Azure CLI and the Test command in Azure PowerShell. For example:
275+
276+
# [Azure CLI](#tab/azure-cli)
277+
278+
```azurecli
279+
az deployment group validate --resource-group <resource-group-name> --template-file <template-file-path>
280+
```
281+
282+
# [Azure PowerShell](#tab/azure-powershell)
283+
284+
```azurepowershell
285+
Test-AzResourceGroupDeployment -ResourceGroupName <ResourceGroupName> -TemplateFile <TemplateFilePath>
286+
```
287+
288+
---
289+
290+
- **What-if**: executes a **What-If** analysis directly from the deployment pane. The pane displays the results, showing any planned changes. This performs the same function as the what-if command in Azure PowerShell and Azure CLI. For example:
291+
292+
# [Azure CLI](#tab/azure-cli)
293+
294+
```azurecli
295+
az deployment group what-if --resource-group <resource-group-name> --template-file <template-file-path>
296+
```
297+
298+
# [Azure PowerShell](#tab/azure-powershell)
299+
300+
```azurepowershell
301+
New-AzResourceGroupDeployment -Whatif -ResourceGroupName <ResourceGroupName> -TemplateFile <TemplateFilePath>
302+
```
303+
304+
---
274305
275306
For more information, see one of the following articles:
276307

0 commit comments

Comments
 (0)