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/load-testing/tutorial-cicd-github-actions.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,15 +56,9 @@ The sample application's source repo includes an Apache JMeter script named *Sam
56
56
57
57
## Set up GitHub access permissions for Azure
58
58
59
-
The GitHub Actions workflow needs to authenticate with Azure to access Azure resources. In the sample application, you use the [Azure Login](https://github.com/Azure/login) action and an Azure Active Directory service principal to authenticate with Azure. For other options to authenticate to Azure, see the [Azure and GitHub integration site](/azure/developer/github).
59
+
The GitHub Actions workflow needs to authenticate with Azure to access Azure resources. In the sample application, you use the [Azure Login](https://github.com/Azure/login) action and an Azure Active Directory service principal to authenticate with Azure.
60
60
61
-
In this section, you'll go through the following steps:
62
-
63
-
- Create an Azure Active Directory service principal with the Contributor role.
64
-
- Add the service principal as a GitHub secret to the sample application repository.
65
-
- Assign the Load Test Contributor role to the service principal.
66
-
67
-
Set up your GitHub repository to have permissions to access your Azure load testing resource:
61
+
In this section, you'll configure your GitHub repository to have permissions to access your Azure load testing resource:
68
62
69
63
1. Run the following Azure CLI command to create a service principal and assign the Contributor role:
70
64
@@ -88,8 +82,13 @@ Set up your GitHub repository to have permissions to access your Azure load test
88
82
}
89
83
```
90
84
85
+
> [!NOTE]
86
+
> Azure Login supports multiple ways to authenticate with Azure. For other authentication options, see the [Azure and GitHub integration site](/azure/developer/github).
87
+
91
88
1. Go to your forked GitHub repository for the sample application.
92
89
90
+
You'll add a GitHub secret to your repository for the service principal you created in the previous step. The Azure Login action uses this secret to authenticate with Azure.
91
+
93
92
1. Add a new secret to your GitHub repository by selecting **Settings** > **Secrets** > **New repository secret**.
94
93
95
94
:::image type="content" source="./media/tutorial-cicd-github-actions/github-new-secret.png" alt-text="Screenshot that shows selections for adding a new repository secret to your GitHub repo.":::
@@ -114,7 +113,7 @@ Set up your GitHub repository to have permissions to access your Azure load test
114
113
--subscription "<subscription-name-or-id>"
115
114
```
116
115
117
-
You can now use the `AZURE_CREDENTIALS` secret with the Azure Login action in your CI/CD workflow. The following code snippet describes how this for the sample application:
116
+
You can now use the `AZURE_CREDENTIALS` secret with the Azure Login action in your CI/CD workflow. The following code snippet describes how this works for the sample application:
0 commit comments