You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/azure/includes/azure-template-pipeline-sign-in.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,15 @@ To work with resource groups in Azure, sign in to your Azure account from the Vi
14
14
15
15
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.
16
16
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.":::
18
18
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**.
20
20
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.":::
22
22
23
23
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.
24
24
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.":::
26
26
27
27
### Sign in to Azure by using the Azure CLI
28
28
@@ -44,15 +44,15 @@ To work with resource groups in Azure, sign in to your Azure account from the Vi
44
44
45
45
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.
46
46
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.":::
48
48
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**.
50
50
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.":::
52
52
53
53
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.
54
54
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.":::
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.
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.
0 commit comments