chore: update readme version to v6.0.0 (#1642)

This commit is contained in:
Henry Griffiths
2026-02-05 11:53:33 -06:00
committed by GitHub
parent bb84b6db01
commit 0f01265ceb

View File

@@ -182,7 +182,7 @@ this action will always consider the `HTTP_PROXY` environment variable.
Manually configured proxy: Manually configured proxy:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
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
@@ -243,7 +243,7 @@ you can use the `transitive-tag-keys` input to specify the keys of the tags to b
_Note that all subsequent roles in the chain must have `role-skip-session-tagging` set to `true`_ _Note that all subsequent roles in the chain must have `role-skip-session-tagging` set to `true`_
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5 uses: aws-actions/configure-aws-credentials@v6
with: with:
transitive-tag-keys: | transitive-tag-keys: |
Repository Repository
@@ -267,13 +267,13 @@ line.
<summary>Inline session policy examples</summary> <summary>Inline session policy examples</summary>
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
inline-session-policy: '{"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:List*","Resource":"*"}]}' inline-session-policy: '{"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:List*","Resource":"*"}]}'
``` ```
Or we can have a nicely formatted JSON as well: Or we can have a nicely formatted JSON as well:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
inline-session-policy: >- inline-session-policy: >-
{ {
@@ -299,13 +299,13 @@ the role.
<summary>Managed session policy examples</summary> <summary>Managed session policy examples</summary>
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
``` ```
And we can pass multiple managed policies likes this: And we can pass multiple managed policies likes this:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
managed-session-policies: | managed-session-policies: |
arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
@@ -343,7 +343,7 @@ You can specify the audience through the `audience` input:
```yaml ```yaml
- name: Configure AWS Credentials for China region audience - name: Configure AWS Credentials for China region audience
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
audience: sts.amazonaws.com.cn audience: sts.amazonaws.com.cn
aws-region: cn-northwest-1 aws-region: cn-northwest-1
@@ -417,7 +417,7 @@ Examples
### AssumeRoleWithWebIdentity ### AssumeRoleWithWebIdentity
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
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
@@ -431,13 +431,13 @@ environment variable and use it to assume the role
### AssumeRole with role previously assumed by action in same workflow ### AssumeRole with role previously assumed by action in same workflow
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
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
role-session-name: MySessionName role-session-name: MySessionName
- name: Configure other AWS Credentials - name: Configure other AWS Credentials
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::987654321000:role/my-second-role role-to-assume: arn:aws:iam::987654321000:role/my-second-role
@@ -454,7 +454,7 @@ Note that the trust relationship/trust policy of the second role must grant the
### AssumeRole with static IAM credentials in repository secrets ### AssumeRole with static IAM credentials in repository secrets
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
@@ -473,7 +473,7 @@ name, like `role-to-assume: my-github-actions-role`.
```yaml ```yaml
- name: Configure AWS Credentials 1 - name: Configure AWS Credentials 1
id: creds id: creds
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
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
@@ -482,7 +482,7 @@ name, like `role-to-assume: my-github-actions-role`.
run: | run: |
aws sts get-caller-identity aws sts get-caller-identity
- name: Configure AWS Credentials 2 - name: Configure AWS Credentials 2
uses: aws-actions/configure-aws-credentials@v5.1.1 uses: aws-actions/configure-aws-credentials@v6.0.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }} aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }}