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
Problem Summary:
When attempting to delete AWS ECR Public Repositories that still contain images using aws-nuke (which currently uses AWS Cloud Control), the operation fails. This issue is specific to the use of the cloud-control API for AWS::ECR::PublicRepository.
cloud-control doesn't delete images inside the repository, so using cloud control in aws-nuke for AWS::ECR::PublicRepository doesn't properly work today.
{
"TypeName": "AWS::ECR::PublicRepository",
"Identifier": "jboss-eap",
"RequestToken": "xxxxxxxx",
"Operation": "DELETE",
"OperationStatus": "FAILED",
"EventTime": "2023-11-17T21:37:11.168000+00:00",
"StatusMessage": "The repository with name 'jboss-eap' in registry with id 'xxxxxx' cannot be deleted because it still contains images (Service: EcrPublic, Status Code: 400, Request ID: xxxxx)",
"ErrorCode": "GeneralServiceException"
},
The text was updated successfully, but these errors were encountered:
fridim
added a commit
to fridim/aws-nuke
that referenced
this issue
Nov 21, 2023
Problem Summary:
When attempting to delete AWS ECR Public Repositories that still contain images using
aws-nuke
(which currently uses AWS Cloud Control), the operation fails. This issue is specific to the use of the cloud-control API for AWS::ECR::PublicRepository.cloud-control doesn't delete images inside the repository, so using cloud control in aws-nuke for
AWS::ECR::PublicRepository
doesn't properly work today.Symptom:
aws-nuke loops forever
aws cloudcontrol list-resource-requests
:The text was updated successfully, but these errors were encountered: