put-image fails when image already exists on repository with tag and is immutable

[daveisfera]

Describe the bug

Following up on this because currently put-image will error out when a build doesn't change the built image and the tag already exists with that image:
aws/aws-sdk#750

Regression Issue

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

Expected Behavior

Have an option to ignore this or an exit code to indicate this issue, because it appears that currently the status code for all errors is 254 so there's no way to tell the difference between a "safe"/expected error and an actual problem

Current Behavior

Errors out with the same status code as all other errors

Reproduction Steps

1. Push an image to a tag
2. Try pushing the same image to the same tag
3. Observe that it fails

Possible Solution

Flag to ignore this error or have different status codes to indicate how it failed

Additional Information/Context

No response

CLI version used

aws-cli/2.24.7

Environment details (OS name and version, etc.)

Python/3.12.9 Darwin/24.3.0 source/x86_64

[khushail]

Hi @daveisfera , thanks for reaching out.

I see you have already files a case for this request with AWS Team -aws/containers-roadmap#2380 as suggested by our teammember earlier.. So IMO if you need any updates, you would have to follow up there.

EDIT: A workaround is also suggested here.

[khushail]

closing this as duplicate as its just a follow up. Request you to post comments on the original issue filed with AWS team. Thanks

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[daveisfera]

That issue is asking that ECR allow those requests when the content is identical and there has been no response.
This issue is requesting that the aws-cli handle this or at least expose a way to handle this so that different types of errors can be handled. Also, the suggested workaround isn't possible, so it's not actually a workaround. I would comment that in that issue but it's been archived so there's not a way to follow up there.
This isn't a duplicate of the other and unless the other is going to be resolved, then this is necessary.

[khushail]

Hi @daveisfera , I tried to repro the issue with put-image command. Sharing what I observed -

1. I am not able to put-images at all with this put-image commnd. Checked the IAM policies, got authenticated with docker , still no success.
2. Tried a workaround to put-images.

• Authenticated with ECR(making sure it has the same region and accountid) -
  aws ecr get-login-password --region <region> | docker login --username AWS --password-stdin <aws_account_id>.dkr.ecr.<region>.amazonaws.com
• checking my reprository in same region
  aws ecr describe-repositories --repository-name my-repo
• alternate to put-image which succeeds first time-
  `docker tag cdk-e9194c9afdbe793e29b1b99a3697fb145cd194a7438f2e4230872465143beef2:latest <aws_account_id>.dkr.ecr..amazonaws.com/my-repo:latest

docker push <aws_account_id>.dkr.ecr..amazonaws.com/my-repo:latest
`

• Redeploying the same image with same tag shows it already exists -

Let me know if its helpful.

I see this issue is open but there has been no action so I would consult with the team on the next steps. will share updates soon.

[daveisfera]

Here's the commands I run that run into the error with ${tag} being defined as the ${branch} that's being deployed and the SHA of the commit that was for that build:

MANIFEST=$(aws ecr batch-get-image --repository-name myorg/myproj --image-ids imageTag="${tag}" --query 'images[].imageManifest' --output text)
aws ecr put-image --repository-name myorg/myproj --image-tag "${branch}" --image-manifest "$MANIFEST"