Skip to content

Commit e951d87

Browse files
TaojunshenTaojunshen
authored
Merge pull request #50925 from MicrosoftDocs/main
6/12/2025 PM Publish
2 parents 652d4a6 + c096973 commit e951d87

File tree

55 files changed

+640
-624
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

55 files changed

+640
-624
lines changed

‎learn-pr/azure/includes/azure-template-pipeline-sign-in.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,15 @@ To work with resource groups in Azure, sign in to your Azure account from the Vi
1414

1515
1. If the shell shown on the right side of the terminal window is **bash**, the correct shell is open and you can skip to the next section.
1616

17-
:::image type="content" source="media/bash.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the bash option shown.":::
17+
:::image type="content" source="media/bash.png" alt-text="Screenshot of the Visual Studio Code terminal window. The bash option is highlighted.":::
1818

19-
1. If a shell other than **bash** appears, select the shell dropdown, and then select **Git Bash (Default)**.
19+
1. If a shell other than **bash** appears, select the shell dropdown arrow, and then select **Git Bash**.
2020

21-
:::image type="content" source="media/select-shell-bash.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the terminal shell dropdown shown and Git Bash Default selected.":::
21+
:::image type="content" source="media/select-shell-bash.png" alt-text="Screenshot of the Visual Studio Code terminal window. The terminal shell dropdown list is shown, and Git Bash selected.":::
2222

2323
1. In the list of terminal shells, select **bash**, and then select the plus sign to open a new terminal that uses the **bash** shell.
2424

25-
:::image type="content" source="media/select-bash-plus.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the bash terminal and the plus sign selected.":::
25+
:::image type="content" source="media/select-bash-plus.png" alt-text="Screenshot of the Visual Studio Code terminal window. The bash terminal and the plus sign are highlighted.":::
2626

2727
### Sign in to Azure by using the Azure CLI
2828

@@ -44,15 +44,15 @@ To work with resource groups in Azure, sign in to your Azure account from the Vi
4444

4545
1. If the shell shown on the right side of the terminal window is **powershell** or **pwsh**, the correct shell is open and you can skip to the next section.
4646

47-
:::image type="content" source="media/pwsh.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the p w s h option displayed in the shell dropdown.":::
47+
:::image type="content" source="media/pwsh.png" alt-text="Screenshot of the Visual Studio Code terminal window. The pwsh option is highlighted.":::
4848

49-
1. If a shell other than **powershell** or **pwsh** appears, select the shell dropdown, and then select **PowerShell**.
49+
1. If a shell other than **powershell** or **pwsh** appears, select the shell dropdown arrow, and then select **PowerShell**.
5050

51-
:::image type="content" source="media/select-shell-powershell.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the terminal shell dropdown shown and PowerShell selected.":::
51+
:::image type="content" source="media/select-shell-powershell.png" alt-text="Screenshot of the Visual Studio Code terminal window. PowerShell is selected in the terminal shell dropdown list.":::
5252

5353
1. In the list of terminal shells, select **powershell** or **pwsh**, and then select the plus sign to open a new terminal that uses the **powershell** or **pwsh** shell.
5454

55-
:::image type="content" source="media/select-powershell-plus.png" alt-text="Screenshot of the Visual Studio Code terminal window, with the PowerShell terminal and the plus sign selected.":::
55+
:::image type="content" source="media/select-powershell-plus.png" alt-text="Screenshot of the Visual Studio Code terminal window. The PowerShell terminal and the plus sign are selected.":::
5656

5757
### Sign in to Azure by using Azure PowerShell
5858

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/1-introduction.yml

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.introduction
3-
title: Introduction
4-
metadata:
5-
unitType: introduction
6-
title: Introduction
7-
description: Introduction to testing Bicep code by using Azure Pipelines.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
durationInMinutes: 2
15-
content: |
16-
[!include[](includes/1-introduction.md)]
17-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.introduction
3+
title: Introduction
4+
metadata:
5+
unitType: introduction
6+
title: Introduction
7+
description: Introduction to testing Bicep code by using Azure Pipelines.
8+
ms.date: 05/29/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
durationInMinutes: 2
15+
content: |
16+
[!include[](includes/1-introduction.md)]
17+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/10-knowledge-check.yml

Lines changed: 53 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,53 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.knowledge-check
3-
title: Module assessment
4-
metadata:
5-
unitType: knowledge_check
6-
title: Module assessment
7-
description: Knowledge check.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
durationInMinutes: 2
15-
content: |
16-
[!include[](includes/10-knowledge-check.md)]
17-
quiz:
18-
questions:
19-
- content: |
20-
What can you do to minimize the chance of this error happening again?
21-
choices:
22-
- content: Add an approval check to the pipeline.
23-
isCorrect: false
24-
explanation: Incorrect. An approval check enables you to manually verify the status of your environment or pipeline. It doesn't reduce the chance of an invalid template being submitted to Azure.
25-
- content: Run preflight validation within your pipeline.
26-
isCorrect: true
27-
explanation: Correct. The preflight validation process performs validation of your template. It reports errors that prevent the template deployment from being submitted to Azure.
28-
- content: Add a rollback stage to your pipeline.
29-
isCorrect: false
30-
explanation: Incorrect. You can add a rollback stage to reverse the effects of a stage that's failed, but it doesn't validate the Bicep file that you submit.
31-
- content: Which of these scenarios is an example of negative testing?
32-
choices:
33-
- content: Manually approving a pipeline run.
34-
isCorrect: false
35-
explanation: Incorrect. However, you might choose to manually run tests and then approve the pipeline run.
36-
- content: Rolling back your deployment if something fails.
37-
isCorrect: false
38-
explanation: Incorrect. However, you might choose to roll back a deployment if your negative tests fail.
39-
- content: Verifying that a website is accessible only through HTTPS and not through HTTP.
40-
isCorrect: true
41-
explanation: Correct. Negative tests verify that your resource doesn't exhibit unwanted behavior, like responding on nonsecure protocols.
42-
- content: Which of these statements is true?
43-
choices:
44-
- content: The Bicep linter needs to be installed separately from Bicep.
45-
isCorrect: false
46-
explanation: Incorrect. The Bicep linter is part of the Bicep tooling. It runs automatically when you build or deploy a Bicep file.
47-
- content: A template with no linting warnings or errors is guaranteed to deploy successfully.
48-
isCorrect: false
49-
explanation: Incorrect. The linter runs some basic checks on code style. Your template might successfully pass the linter's checks, but not deploy.
50-
- content: Linting ensures that your Bicep file meets a minimum quality level for code style.
51-
isCorrect: true
52-
explanation: Correct. The linter doesn't verify that your file will deploy successfully, but it checks that your Bicep file follows some basic rules for code style.
53-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.knowledge-check
3+
title: Module assessment
4+
metadata:
5+
unitType: knowledge_check
6+
title: Module assessment
7+
description: Knowledge check.
8+
ms.date: 05/30/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
durationInMinutes: 2
15+
content: |
16+
[!include[](includes/10-knowledge-check.md)]
17+
quiz:
18+
questions:
19+
- content: |
20+
What can you do to minimize the chance of this error happening again?
21+
choices:
22+
- content: Add an approval check to the pipeline.
23+
isCorrect: false
24+
explanation: Incorrect. An approval check enables you to manually verify the status of your environment or pipeline. It doesn't reduce the chance of an invalid template being submitted to Azure.
25+
- content: Run preflight validation in your pipeline.
26+
isCorrect: true
27+
explanation: Correct. The preflight validation process performs validation of your template. It reports errors that prevent the template deployment from being submitted to Azure.
28+
- content: Add a rollback stage to your pipeline.
29+
isCorrect: false
30+
explanation: Incorrect. You can add a rollback stage to reverse the effects of a stage that fails, but that stage doesn't validate the Bicep file that you submit.
31+
- content: Which of these scenarios is an example of negative testing?
32+
choices:
33+
- content: Manually approving a pipeline run.
34+
isCorrect: false
35+
explanation: Incorrect. However, you might choose to manually run tests and then approve the pipeline run.
36+
- content: Rolling back your deployment if something fails.
37+
isCorrect: false
38+
explanation: Incorrect. However, you might choose to roll back a deployment if your negative tests fail.
39+
- content: Verifying that a website is accessible only through HTTPS and not through HTTP.
40+
isCorrect: true
41+
explanation: Correct. Negative tests verify that your resource doesn't exhibit unwanted behavior, like responding on nonsecure protocols.
42+
- content: Which of these statements is true?
43+
choices:
44+
- content: The Bicep linter needs to be installed separately from Bicep.
45+
isCorrect: false
46+
explanation: Incorrect. The Bicep linter is part of the Bicep tooling. It runs automatically when you build or deploy a Bicep file.
47+
- content: A template with no linting warnings or errors is guaranteed to deploy successfully.
48+
isCorrect: false
49+
explanation: Incorrect. The linter runs some basic checks on code style. Your template might successfully pass the linter's checks but not deploy.
50+
- content: Linting ensures that your Bicep file meets a minimum quality level for code style.
51+
isCorrect: true
52+
explanation: Correct. The linter doesn't verify that your file will deploy successfully, but it checks that your Bicep file follows some basic rules for code style.
53+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/11-summary.yml

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.summary
3-
title: Summary
4-
metadata:
5-
unitType: summary
6-
title: Summary
7-
description: Summary for testing your Bicep code by using Azure Pipelines.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
durationInMinutes: 1
15-
content: |
16-
[!include[](includes/11-summary.md)]
17-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.summary
3+
title: Summary
4+
metadata:
5+
unitType: summary
6+
title: Summary
7+
description: Summary for testing your Bicep code by using Azure Pipelines.
8+
ms.date: 05/30/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
durationInMinutes: 1
15+
content: |
16+
[!include[](includes/11-summary.md)]
17+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/2-understand-pipeline-stages.yml

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.understand-pipeline-stages
3-
title: Understand pipeline stages
4-
metadata:
5-
unitType: learning-content
6-
title: Understand pipeline stages
7-
description: Learn about multistage pipelines in Azure Pipelines. Also, learn about the typical deployment stages for Bicep code.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
durationInMinutes: 7
15-
content: |
16-
[!include[](includes/2-understand-pipeline-stages.md)]
17-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.understand-pipeline-stages
3+
title: Understand pipeline stages
4+
metadata:
5+
unitType: learning-content
6+
title: Understand pipeline stages
7+
description: Learn about multistage pipelines in Azure Pipelines. Also, learn about the typical deployment stages for Bicep code.
8+
ms.date: 05/29/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
durationInMinutes: 7
15+
content: |
16+
[!include[](includes/2-understand-pipeline-stages.md)]
17+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/3-lint-validate-bicep-code.yml

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.lint-validate-bicep-code
3-
title: Lint and validate your Bicep code
4-
metadata:
5-
unitType: learning-content
6-
title: Lint and validate your Bicep code
7-
description: Learn about linting and validating your Bicep code in a deployment pipeline.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
zone_pivot_groups: azure-shell-interface
15-
durationInMinutes: 5
16-
content: |
17-
[!include[](includes/3-lint-validate-bicep-code.md)]
18-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.lint-validate-bicep-code
3+
title: Lint and validate your Bicep code
4+
metadata:
5+
unitType: learning-content
6+
title: Lint and validate your Bicep code
7+
description: Learn about linting and validating your Bicep code in a deployment pipeline.
8+
ms.date: 05/29/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
zone_pivot_groups: azure-shell-interface
15+
durationInMinutes: 5
16+
content: |
17+
[!include[](includes/3-lint-validate-bicep-code.md)]
18+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/4-exercise-set-up-environment.yml

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.exercise-set-up-environment
3-
title: Exercise - Set up your environment
4-
metadata:
5-
unitType: exercise
6-
title: Exercise - Set up your environment
7-
description: Configure your environment to add tests to your Bicep deployment pipeline.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
zone_pivot_groups: azure-shell-interface
15-
durationInMinutes: 4
16-
content: |
17-
[!include[](includes/4-exercise-set-up-environment.md)]
18-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.exercise-set-up-environment
3+
title: Exercise - Set up your environment
4+
metadata:
5+
unitType: exercise
6+
title: Exercise - Set up your environment
7+
description: Configure your environment so you can add tests to your Bicep deployment pipeline.
8+
ms.date: 05/29/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
zone_pivot_groups: azure-shell-interface
15+
durationInMinutes: 4
16+
content: |
17+
[!include[](includes/4-exercise-set-up-environment.md)]
18+

‎learn-pr/azure/test-bicep-code-using-azure-pipelines/5-exercise-add-lint-validate-stages-pipeline.yml

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
### YamlMime:ModuleUnit
2-
uid: learn.azure.test-bicep-code-using-azure-pipelines.exercise-add-lint-validate-stages-pipeline
3-
title: Exercise - Add lint and validate stages to your pipeline
4-
metadata:
5-
unitType: exercise
6-
title: Exercise - Add lint and validate stages to your pipeline
7-
description: Add Bicep linting and preflight validation to your Bicep deployment pipeline.
8-
ms.date: 10/31/2022
9-
author: mumian
10-
ms.author: jgao
11-
ms.topic: unit
12-
ms.custom:
13-
- devx-track-bicep
14-
durationInMinutes: 3
15-
content: |
16-
[!include[](includes/5-exercise-add-lint-validate-stages-pipeline.md)]
17-
1+
### YamlMime:ModuleUnit
2+
uid: learn.azure.test-bicep-code-using-azure-pipelines.exercise-add-lint-validate-stages-pipeline
3+
title: Exercise - Add lint and validate stages to your pipeline
4+
metadata:
5+
unitType: exercise
6+
title: Exercise - Add lint and validate stages to your pipeline
7+
description: Add Bicep linting and preflight validation to your Bicep deployment pipeline.
8+
ms.date: 05/30/2025
9+
author: mumian
10+
ms.author: jgao
11+
ms.topic: unit
12+
ms.custom:
13+
- devx-track-bicep
14+
durationInMinutes: 3
15+
content: |
16+
[!include[](includes/5-exercise-add-lint-validate-stages-pipeline.md)]
17+

0 commit comments

Comments
 (0)