Merge pull request #687 from fabienfoerster/patch-2

Update README examples to use v2
This commit is contained in:
Peter Woodworth
2023-03-07 17:36:19 -08:00
committed by GitHub

View File

@@ -77,7 +77,7 @@ jobs:
run: | run: |
aws s3 sync . s3://my-s3-test-website-bucket aws s3 sync . s3://my-s3-test-website-bucket
- name: Configure AWS credentials from Production account - name: Configure AWS credentials from Production account
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
role-to-assume: arn:aws:iam::222222222222:role/my-github-actions-role-prod role-to-assume: arn:aws:iam::222222222222:role/my-github-actions-role-prod
aws-region: us-west-2 aws-region: us-west-2
@@ -159,7 +159,7 @@ In this example, the secret `AWS_ROLE_TO_ASSUME` contains a string like `arn:aws
#### AssumeRoleWithWebIdentity using a custom audience #### AssumeRoleWithWebIdentity using a custom audience
```yaml ```yaml
- name: Configure AWS Credentials for Beta Customers - name: Configure AWS Credentials for Beta Customers
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
audience: beta-customers audience: beta-customers
aws-region: us-east-3 aws-region: us-east-3
@@ -173,7 +173,7 @@ Changing the default audience may be necessary when using non-default [AWS parti
#### AssumeRoleWithWebIdentity and disable secure Action outputs #### AssumeRoleWithWebIdentity and disable secure Action outputs
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
@@ -292,7 +292,7 @@ the OIDC provider and not set during the AssumeRoleWithWebIdentity API call
within the Action. You can skip this session tagging by providing within the Action. You can skip this session tagging by providing
`role-skip-session-tagging` as true in the action's inputs: `role-skip-session-tagging` as true in the action's inputs:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
role-skip-session-tagging: true role-skip-session-tagging: true
``` ```
@@ -314,7 +314,7 @@ You can use this action to simply configure the region and account ID in the
environment, and then use the runner's credentials for all AWS API calls made by environment, and then use the runner's credentials for all AWS API calls made by
your Actions workflow: your Actions workflow:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
aws-region: us-east-2 aws-region: us-east-2
``` ```
@@ -347,7 +347,7 @@ environment.
Manually configured proxy: Manually configured proxy:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v1 uses: aws-actions/configure-aws-credentials@v2
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: my-github-actions-role role-to-assume: my-github-actions-role