From 3654e67612e5261e033cff091dd3a2830d17b9c2 Mon Sep 17 00:00:00 2001 From: Michael Kenntenich <37703728+mkennten@users.noreply.github.com> Date: Wed, 14 Jun 2023 14:26:33 +0200 Subject: [PATCH] Changed texts for step 8, fixing issue --- ...AZ400_M04_L07_Controlling_Deployments_using_Release_Gates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/AZ400_M04_L07_Controlling_Deployments_using_Release_Gates.md b/Instructions/Labs/AZ400_M04_L07_Controlling_Deployments_using_Release_Gates.md index dc0a1e328..adcdc5211 100644 --- a/Instructions/Labs/AZ400_M04_L07_Controlling_Deployments_using_Release_Gates.md +++ b/Instructions/Labs/AZ400_M04_L07_Controlling_Deployments_using_Release_Gates.md @@ -207,7 +207,7 @@ In this task, you will set up the release tasks as part of the Release Pipeline. > **Note**: The pipeline now contains two stages named **Canary** and **Production**. 7. On the **Pipeline** tab, select the **Add an Artifact** rectangle, and select the **eShopOnWeb** in the **Source (build pipeline)** field. Click **Add** to confirm the selection of the artifact. -8. From the **Artifact** rectangle, notice the **Continuous Integration Trigger** (lightning bolt) appearing. Click it to open the **Continuous deployment trigger** settings. Click the continuous deployment trigger to toggle the switch to enable it. Leave all other settings at default and close the **Continuous deployment trigger** pane, by clicking the **x** mark in its upper right corner. +8. From the **Artifacts** rectangle, notice the **Continuous deployment trigger** (lightning bolt). Click it to open the **Continuous deployment trigger** settings. Click **Disabled** to toggle the switch and enable it. Leave all other settings at default and close the **Continuous deployment trigger** pane, by clicking the **x** mark in its upper right corner. 9. Within the **Canary Environments** stage, click the **1 job, 2 tasks** label and review the tasks within this stage. > **Note**: The canary environment has 1 task which, respectively, publishes the artifact package to Azure Web App.