Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not recognizing inputs for configuring credentials #1158

Closed
1 task
mikeheft opened this issue Sep 17, 2024 · 2 comments
Closed
1 task

Not recognizing inputs for configuring credentials #1158

mikeheft opened this issue Sep 17, 2024 · 2 comments
Labels
bug Something isn't working closed-for-staleness response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 5 days.

Comments

@mikeheft
Copy link

Describe the bug

I am receiving an error in my action logs about an error:

> Run aws-actions/configure-aws-credentials@v4
  with:
    audience: sts.amazonaws.com
  Error: Input required and not supplied: aws-region

However, here is my job step. I had it set with ${{ secrets.AWS_REGION }} but that was failing as well, so I hard coded it.

permissions:
  id-token: write
  contents: read
steps:
  - name: Set up AWS credentials
    uses: aws-actions/configure-aws-credentials@v4
    with:
      aws-region: us-west-2
      aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
      aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

Here are the logs from that step. The secrets in question are all set properly. This was working previously then I moved it to a reusable workflow and that is when it started to fail.

##[debug]Evaluating condition for step: 'Set up AWS credentials'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Set up AWS credentials
##[debug]Register post job cleanup for action: aws-actions/configure-aws-credentials@v4
##[debug]Loading inputs
##[debug]Evaluating: secrets.AWS_ACCESS_KEY_ID
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'AWS_ACCESS_KEY_ID'
##[debug]=> null
##[debug]Result: null
##[debug]Evaluating: secrets.AWS_SECRET_ACCESS_KEY
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'AWS_SECRET_ACCESS_KEY'
##[debug]=> null
##[debug]Result: null
##[debug]Evaluating: secrets.AWS_REGION
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'AWS_REGION'
##[debug]=> null
##[debug]Result: null
##[debug]Loading env
Run aws-actions/configure-aws-credentials@v4
Error: Input required and not supplied: aws-region
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: Set up AWS credentials

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

Expected it to configure the credentials successfully as it did previously

Current Behavior

> Run aws-actions/configure-aws-credentials@v4
  with:
    audience: sts.amazonaws.com
  Error: Input required and not supplied: aws-region

Reproduction Steps

  • Add secrets to repo
  • Create an action
  • Ensure Action has read/write permissions
  • Run action
  • Fails

Possible Solution

No response

Additional Information/Context

The secrets in question are all set properly. This was working previously then I moved it to a reusable workflow and that is when it started to fail.

@mikeheft mikeheft added bug Something isn't working needs-triage This issue still needs to be triaged labels Sep 17, 2024
@kellertk
Copy link
Contributor

Your run output indicates that your secrets aren't being picked up at all by the action run. Are you sure you have permissions to read them? Organization-level secrets might have different permissions and secrets aren't populated to forked repositories. Please review https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions

@kellertk kellertk added response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 5 days. and removed needs-triage This issue still needs to be triaged labels Oct 15, 2024
Copy link

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 2 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 2 days unless further comments are made. labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working closed-for-staleness response-requested Waiting on additional info and feedback. Will move to 'closing-soon' in 5 days.
Projects
None yet
Development

No branches or pull requests

2 participants