-
Notifications
You must be signed in to change notification settings - Fork 402
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
Maintenance: Review pipeline to update the aws-actions/configure-aws-credentials action #3025
Comments
We merged the change and confirmed that the new version works: aws-powertools/powertools-lambda-typescript#1662 Another change in 3.x is that you now have to pass |
Hello @dreamorosi! Thank you so much for sharing this. I think our issue is with this 🚀 |
Adding |
This was updated in V3 pipeline! Closing. |
|
Why is this needed?
The v3 major version of aws-actions/configure-aws-credentials has been released and is breaking our CI.
The role assumed in https://github.com/aws-powertools/powertools-lambda-python/blob/develop/.github/workflows/reusable_deploy_v2_sar.yml#L182 is different from the role that should be outputted by this command https://github.com/aws-powertools/powertools-lambda-python/blob/develop/.github/workflows/reusable_deploy_v2_sar.yml#L103.
Also, accountid is not masked by default and need to add special configuration to avoid problems with special characters (https://github.com/aws-actions/configure-aws-credentials#special-characters-in-aws_secret_access_key).
Which area does this relate to?
Automation
Solution
Investigate these problems before update this dependency.
Acknowledgment
The text was updated successfully, but these errors were encountered: