|
2 | 2 | title: CI/CD with Azure Pipelines and templates
|
3 | 3 | description: Describes how to configure continuous integration in Azure Pipelines by using Azure Resource Manager templates. It shows how to use a PowerShell script, or copy files to a staging location and deploy from there.
|
4 | 4 | ms.topic: conceptual
|
5 |
| -ms.date: 03/09/2021 |
| 5 | +ms.date: 02/07/2022 |
6 | 6 | ---
|
7 | 7 | # Integrate ARM templates with Azure Pipelines
|
8 | 8 |
|
@@ -172,20 +172,20 @@ The following YAML shows the [Azure Resource Manager template deployment task](h
|
172 | 172 |
|
173 | 173 | There are several parts of this task to review in greater detail.
|
174 | 174 |
|
175 |
| -- `deploymentScope`: Select the scope of deployment from the options: `Management Group`, `Subscription`, and `Resource Group`. To learn more about the scopes, see [Deployment scopes](deploy-rest.md#deployment-scope). |
| 175 | +* `deploymentScope`: Select the scope of deployment from the options: `Management Group`, `Subscription`, and `Resource Group`. To learn more about the scopes, see [Deployment scopes](deploy-rest.md#deployment-scope). |
176 | 176 |
|
177 |
| -- `azureResourceManagerConnection`: Provide the name of the service connection you created. |
| 177 | +* `azureResourceManagerConnection`: Provide the name of the service connection you created. |
178 | 178 |
|
179 |
| -- `subscriptionId`: Provide the target subscription ID. This property only applies to the Resource Group deployment scope and the subscription deployment scope. |
| 179 | +* `subscriptionId`: Provide the target subscription ID. This property only applies to the Resource Group deployment scope and the subscription deployment scope. |
180 | 180 |
|
181 |
| -- `resourceGroupName` and `location`: provide the name and location of the resource group you want to deploy to. The task creates the resource group if it doesn't exist. |
| 181 | +* `resourceGroupName` and `location`: provide the name and location of the resource group you want to deploy to. The task creates the resource group if it doesn't exist. |
182 | 182 |
|
183 | 183 | ```yml
|
184 | 184 | resourceGroupName: '<resource-group-name>'
|
185 | 185 | location: '<location>'
|
186 | 186 | ```
|
187 | 187 |
|
188 |
| -- `csmFileLink`: Provide the link for the staged template. When setting the value, use variables returned from the file copy task. The following example links to a template named mainTemplate.json. The folder named **templates** is included because that where the file copy task copied the file to. In your pipeline, provide the path to your template and the name of your template. |
| 188 | +* `csmFileLink`: Provide the link for the staged template. When setting the value, use variables returned from the file copy task. The following example links to a template named mainTemplate.json. The folder named **templates** is included because that where the file copy task copied the file to. In your pipeline, provide the path to your template and the name of your template. |
189 | 189 |
|
190 | 190 | ```yml
|
191 | 191 | csmFileLink: '$(AzureFileCopy.StorageContainerUri)templates/mainTemplate.json$(AzureFileCopy.StorageContainerSasToken)'
|
@@ -224,7 +224,7 @@ steps:
|
224 | 224 | deploymentName: 'deploy1'
|
225 | 225 | ```
|
226 | 226 |
|
227 |
| -When you select **Save**, the build pipeline is automatically run. Go back to the summary for your build pipeline, and watch the status. |
| 227 | +When you select **Save**, the build pipeline is automatically run. Under the **Jobs** frame, select **Job** to see the job status. |
228 | 228 |
|
229 | 229 | ## Next steps
|
230 | 230 |
|
|
0 commit comments