Action overrides AWS env vars for subsequent running action about configure-aws-credentials

[clareliguori]

Hi @nicolaevladescu , I don't know the order of precedence that GitHub Actions follows for setting env variables in Docker actions (I can't find it documented anywhere), but it appears that env vars set in the workflow's environment override values in the action's env settings based on what you are seeing. It would be a good question for you to ask in the GitHub Actions forum.

Do you see the same behavior for any kind of environment variable, not just ones set by this action? For example, does "bar" take precedence over both "foo" and "baz" below?

jobs:
  job1:
    env:
      AWS_ACCESS_KEY_ID: "foo"
    steps:
    - run: |
       echo "::set-env name=AWS_ACCESS_KEY_ID::bar"
    - uses: <<your action>>
      with:
        aws_key: "baz"

With respect to resetting the environment variables, individual GitHub Action jobs each have a fresh environment, so you can do:

jobs:
  job1:
    runs-on: ubuntu-latest
    steps:
    - uses: aws-actions/configure-aws-credentials@v1
      with:
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws-region: us-east-2
  job2:
    runs-on: ubuntu-latest
    steps:
    - uses: <<your action>>
      with:
        aws_key: ${{ secrets.ANOTHER_AWS_ACCESS_KEY_ID }}
        aws_secret: ${{ secrets.ANOTHER_AWS_SECRET_ACCESS_KEY }}
        aws_region: us-east-2

[nicolaevladescu]

Hi.

Thank you for the suggestions, yeah it seems it's out of the control of this action. I will try to find out the precedence from GitHub.

Thanks for the feedback!