Description
Hello,
I have the following step:
- name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v1
with:
aws-region: ${{ env.TF_VAR_aws_region }}
audience: custom-audience-string
role-to-assume: ${{ secrets.ROLE_ARN }}
role-session-name: ${{ env.GITHUB_SHA }}
With the audience
line, the job returns:
Warning: Unexpected input(s) 'audience', valid inputs are ['aws-access-key-id', 'aws-secret-access-key', 'aws-session-token', 'aws-region', 'mask-aws-account-id', 'role-to-assume', 'web-identity-token-file', 'role-duration-seconds', 'role-session-name', 'role-external-id', 'role-skip-session-tagging']
My IAM OIDC provider is configured to accept the custom-audience-string
but it looks like it's not even making it there
Everything works fine if I omit the audience
argument, but I was hoping to use one OIDC provider for multiple workflows using multiple audiences. I don't understand why I'm getting this error when audience
is both documented and present in the code.
Probably missing something silly because it's Friday afternoon but... please point me to it? Thank you :)