[ECR] [request]: Generate SOCI indexes automatically
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
I would like for ECR to automatically generate SOCI indexes for all pushed images. This way, I do not have to change all my pipelines, and can benefit from SOCI without any additional configuration,.
**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?**
We have thousands of pipelines which build containers and changing them all to build and push SOCI indexes would be painful.
**Are you currently working around this issue?**
Changing each pipeline, but many teams don't know about benefits of SOCI.
**Additional context**
Thanks!
**Attachments**
Contributor guide
Research direction
The request concerns ECR automatically generating SOCI indexes for pushed container images, but it names no repository files, tests, or entry points. Start by researching ECR image-push behavior and SOCI index generation, then define the automatic workflow and verify that existing pipelines can benefit without configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100