You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the support to login ECR needs access token and secret access token to AWS, and the action cannot detect credentials from environment variables as aws-actions/amazon-ecr-login does. The limitation prevents the usage in runner using GitHub OIDC to authenticate with AWS since it holds a temporary credential, and making authentication with temporary credential must include the session token.
My recommendation is to take an optional input of session token, or detect credentials from environment variables as well.
Version
redhat-actions/push-to-registry@v2
aws-actions/configure-aws-credentials@v4
Describe the bug
Currently the support to login ECR needs access token and secret access token to AWS, and the action cannot detect credentials from environment variables as aws-actions/amazon-ecr-login does. The limitation prevents the usage in runner using GitHub OIDC to authenticate with AWS since it holds a temporary credential, and making authentication with temporary credential must include the session token.
My recommendation is to take an optional input of session token, or detect credentials from environment variables as well.
Steps to reproduce, workflow links, screenshots
The text was updated successfully, but these errors were encountered: