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: articles/azure-resource-manager/templates/deploy-github-actions.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
title: Deploy Resource Manager templates by using GitHub Actions
3
3
description: Describes how to deploy Azure Resource Manager templates by using GitHub Actions.
4
4
ms.topic: conceptual
5
-
ms.date: 05/01/2020
5
+
ms.date: 05/05/2020
6
6
---
7
7
8
8
# Deploy Azure Resource Manager templates by using GitHub Actions
9
9
10
-
[GitHub Actions](https://help.github.com/en/actions) enables you to create custom software development life-cycle workflows directly in your GitHub repository where your Azure Resource Manager (ARM) templates are stored. A [workflow](https://help.github.com/actions/reference/workflow-syntax-for-github-actions) is defined by a YAML file. Workflows have one or more jobs with each job containing a set of steps that perform individual tasks. Steps can run commands or use an action. You can create your own actions or use actions shared by the [GitHub community](https://github.com/marketplace?type=actions) and customize them as needed. This article shows how to use an action called [Azure Resource Manager Template Deployment JS](https://github.com/marketplace/actions/azure-resource-manager-arm-template-deployment-js) to deploy Resource Manager templates.
10
+
[GitHub Actions](https://help.github.com/en/actions) enables you to create custom software development life-cycle workflows directly in your GitHub repository where your Azure Resource Manager (ARM) templates are stored. A [workflow](https://help.github.com/actions/reference/workflow-syntax-for-github-actions) is defined by a YAML file. Workflows have one or more jobs with each job containing a set of steps that perform individual tasks. Steps can run commands or use an action. You can create your own actions or use actions shared by the [GitHub community](https://github.com/marketplace?type=actions) and customize them as needed. This article shows how to use [Azure CLI Action](https://github.com/marketplace/actions/azure-cli-action) to deploy Resource Manager templates.
11
11
12
-
The [ARM Template Deployment JS action](https://github.com/marketplace/actions/azure-resource-manager-arm-template-deployment-js) has two dependent actions:
12
+
Azure CLI Action has two dependent actions:
13
13
14
14
-**[Checkout](https://github.com/marketplace/actions/checkout)**: Check out your repository so the workflow can access any specified Resource Manager template.
15
15
-**[Azure Login](https://github.com/marketplace/actions/azure-login)**: Log in with your Azure credentials
@@ -110,11 +110,12 @@ You can either create a workflow file and then push/upload the file to the repos
110
110
with:
111
111
creds: ${{ secrets.AZURE_CREDENTIALS }}
112
112
113
+
113
114
- name: Deploy ARM Template
114
-
uses: whiteducksoftware/azure-arm-action-js@v1
115
+
uses: azure/CLI@v1
115
116
with:
116
-
resourceGroupName: myResourceGroup
117
-
templateLocation:./templates/azuredeploy.json
117
+
inlineScript: |
118
+
az deployment group create --resource-group myResourceGroup --template-file ./templates/azuredeploy.json
118
119
```
119
120
120
121
The workflow file has three sections:
@@ -134,7 +135,8 @@ You can either create a workflow file and then push/upload the file to the repos
134
135
- **Deploy ARM template**. Replace the value of **resourceGroupName**. If you used the Azure CLI script in [Configure deployment credentials](#configure-deployment-credentials), the generated resource group name is the project name with **rg** appended. Verify the value of **templateLocation**.
135
136
136
137
1. Select **Start commit**.
137
-
1. Select **Commit new file**.
138
+
1. Select **Commit directly to the master branch**.
139
+
1. Select **Commit new file** (or **Commit changes**).
138
140
139
141
Because the workflow is configured to be triggered by either the workflow file or the template file being updated, the workflow starts right after you commit the changes.
0 commit comments