AWS custom key names about aws-ecr-orb HOT 5 CLOSED

The issue it still exist even 6.2.0 version.
If "AWS_ACCESS_KEY_ID" is defined in the environment variables but another variable name defined in the job "FANCY_AWS_ACCESS_KEY_ID_1"

      - Build and push image:
          repo_name: myRepo
          aws_account: "22222222222222"
          aws_access_key: FANCY_AWS_ACCESS_KEY_ID_1

It will use "AWS_ACCESS_KEY_ID" from the variables rather then "FANCY_AWS_ACCESS_KEY_ID_1" , same for secret key.

I made it work only removing the default one "AWS_ACCESS_KEY_ID" from env variables and always using customs name for aws variables.

from aws-ecr-orb.

I have experienced same kind of problem, too.

I reported this issue to one of CircleCI support team member and I got message from him that he would create ticket on their BTS, so dev team might investigate on this issue.

Hope I could get reply from him, but I am not sure if dev team would really work on this issue.

from aws-ecr-orb.

so, what is the specific ask here ? you should already be able to simply pass in different environment variable names to these parameters

from aws-ecr-orb.

I am sorry, I didn't realize that this is fixed.

The status of this issue is still open so that the behavior mentioned on this issue is same as I have experienced on my orb project.

I got message from CircleCI support team, and the solution they suggested is exactly same as what is done in this orb.

from aws-ecr-orb.

Closing this as seems API has changed since reporting, and aws-access-key-id and aws-secret-access-key will be properly used if overriden from default env var names.

from aws-ecr-orb.