Skip to content

Commit 6a128a0

Browse files
committed
update
1 parent 8ab82ff commit 6a128a0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -250,15 +250,15 @@ 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. There are two ways to open the deployment pane
253+
1. There are two ways to open the deployment pane:
254254

255255
- Select the show deployment pane button on the upper right corner as shown in the following screenshot:
256256

257257
:::image type="content" source="./media/visual-studio-code/visual-studio-code-open-deployment-pane.png" alt-text="Sceenshot of the open deployment pane button.":::
258258

259259
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.
260260

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**.
261+
- Another way to open the deployment pane is through the command palette. Press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd>, then select either **Show Deployment Pane** or **Show Deployment Pane to the Side**.
262262

263263
:::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.":::
264264

@@ -271,7 +271,7 @@ To use deployment pane:
271271
1. Select your desired action - **Deploy**, **Validate**, or **What-if**.
272272

273273
- **Deploy**: deploys to Azure, and the result including the defined output are shown in the deployment pane.
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:
274+
- **Validate**: performs a runtime validation of the Bicep file against Azure, ensuring that the resources, parameters, and policies are correct in the actual deployment environment. Unlike a [linter](./linter.md), which only checks for syntax errors, this validation interacts with Azure to detect potential deployment issues. It's equivalent to the validate command in Azure CLI and the Test command in Azure PowerShell. For example:
275275

276276
# [Azure CLI](#tab/azure-cli)
277277

0 commit comments

Comments
 (0)