Open fortejas opened 5 years ago
Thanks for your feedback. You're right: we support this in our web UX today, but it's done client side, and we should support this in our APIs, too. I don't have a date for this right now. I'd encourage others to vote for the issue to help us determine its relative priority.
The API is very slow with a large number of images, the ability to filter out using name would be a great help.
@jtoberon any update here by chance?
@fortejas can you share if filtering by “repository tag” or “repository name” is more helpful? Would like to hear from others on their thoughts as well.
@arunsollet Would absolutely love the ability to be able to filter by repository tag.
👍 It would be great if describe-images
had server-side filters on imagePushedAt
/imageScanCompletedAt
start and end times so clients could query for images in particular ranges.
And 💯 being able to specify a server-side sort any of the datetime fields in the response object would be super helpful.
+1 to regex filtering of repo names and filtering by tags
This feature would be really very nice.
Filtering would be useful to distinguish between repositories that store Docker image and Helm packages.
Been 5 years and still open?
Tell us about your request The CLI supports pagination on the
aws ecr describe-repositories
call (docs) but I would like support for filtering, searching and sorting on the ECR APIs. The syntax would be similar to the EC2describe-instances
filters (docs).Which service(s) is this request for? ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
With the default limit of 10000 repos and 10000 images (docs), being able to sort, filter and search for images and repos would be extremely useful.
Are you currently working around this issue?
Currently, the whole list needs to be filtered, sorted and searched client-side via the
--query
option,jq
or a custom script using the SDKs.