serverless / serverless/serverless
ECR support leaves untagged, unused images in the repository
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
ECR images can be very large (up to 10GB) and keeping them around in the registry over time is a waste.
Either they should be cleaned up after each deploy or you could apply an ECR Lifecycle rule that expires them after 1 day pretty easily.
Example:
{
"rules": [
{
"rulePriority": 1,
"description": "Deletes untagged images after 1 day",
"selection": {
"tagStatus": "untagged",
"countType": "sinceImagePushed",
"countUnit": "days",
"countNumber": 1
},
"action": {
"type": "expire"
}
}
]
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing ECR support and how deployment-created images are managed. Confirm whether the implementation should delete untagged images after deployment or apply the provided one-day ECR Lifecycle rule; done means unused untagged images are cleaned up as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100