mirror of
https://github.com/azure/login.git
synced 2026-06-08 22:47:11 +00:00
Update README.md
This commit is contained in:
parent
14a755a4e2
commit
5d09f4d5ca
1 changed files with 7 additions and 0 deletions
|
|
@ -220,6 +220,13 @@ Follow the steps to configure Azure Service Principal with a secret:
|
|||
```
|
||||
* Now in the workflow file in your branch: `.github/workflows/workflow.yml` replace the secret in Azure login action with your secret (Refer to the example above)
|
||||
* Note: The above `az ad sp create-for-rbac` command will give you the `--sdk-auth` deprecation warning. As we are working with CLI for this deprecation process, we strongly recommend users to use this `--sdk-auth` flag as the result dictionary output changes and not accepted by login action if `--sdk-auth` is not used.
|
||||
* If you want to pass Subscription ID, Tenant ID, Client ID, and Client Secret as individual parameters instead of bundling them in a single JSON object (creds) for Non-OIDC login, below snippet can help with the same.
|
||||
```yaml
|
||||
- uses: Azure/login@v1.1
|
||||
with:
|
||||
creds: '{"clientId":"${{ secrets.CLIENT_ID }}","clientSecret":"${{ secrets.CLIENT_SECRET }}","subscriptionId":"${{ secrets.SUBSCRIPTION_ID }}","tenantId":"${{ secrets.TENANT_ID }}"}'
|
||||
```
|
||||
In a similar way, any additional parameter can be addded to creds such as resourceManagerEndpointUrl for Azure Stack, for example.
|
||||
|
||||
### Manually creating the Credentials object
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue