First of all, thank you for developing this action; it's been very useful.
I would like to request the addition of OpenID Connect (OIDC) authentication support. Currently, authentication is only possible via AWS access keys, which requires managing long-term credentials. By implementing OIDC, users can leverage GitHub's built-in OIDC support to obtain short-lived credentials securely.
Additionally, it would be great if the action could accept credentials from a previous job in the workflow. This way, a prior action could handle the authentication, and then kciter/aws-ecr-action could perform the image push without needing to authenticate again. This would provide more flexibility in handling authentication within the GitHub Actions workflow.
First of all, thank you for developing this action; it's been very useful.
I would like to request the addition of OpenID Connect (OIDC) authentication support. Currently, authentication is only possible via AWS access keys, which requires managing long-term credentials. By implementing OIDC, users can leverage GitHub's built-in OIDC support to obtain short-lived credentials securely.
Additionally, it would be great if the action could accept credentials from a previous job in the workflow. This way, a prior action could handle the authentication, and then kciter/aws-ecr-action could perform the image push without needing to authenticate again. This would provide more flexibility in handling authentication within the GitHub Actions workflow.