containers-roadmap
containers-roadmap copied to clipboard
aws
[ECR] [request]: Repository create on push
Community Note
- Please vote on this issue by adding a 👍 reaction 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 When pushing an image, create the repository automatically if it doesn't exist.
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? Before pushing an image, I need to first create the repository which adds friction.
Are you currently working around this issue? Creating the repository before push
Additional context
- https://github.com/awslabs/amazon-ecr-credential-helper/issues/209
- https://stackoverflow.com/questions/51028677/create-aws-ecr-repository-if-it-doesnt-exist
It would be very useful if auto created repositories could also have resource policies attached when they are created.
@joshrivers thanks for the great input! We're thinking of doing that as part of #799
This feature works really well in artifactory and nexus and would be helpful in automated scripts if pushing to ECR. Right now if the entire path does not exist and you try to push into ECR, an EOF error is thrown which is not very easy to debug if you are coming from one of these other products where this feature is baked into docker push.
Just to add, this is something other cloud providers support (GCP) and makes them (GCR) a much better host for images in our multi cloud setup.
+1 for the feature. I can't imagine why AWS already didn't implement this, atleast as a optional setting in ECR. This improves developer experience hugely.
+1 Auto-Create Repository on Push is really expected and important feature from registry service, it is really critical to have it from the box (like the other competitors have) AWS team - please implement that feature for your community! Thanks!
This is the largest blocker for us in fully transitioning to ECR.
Unbelievable it doesn't exist yet...
+1 it is a blocker for me to move to ECR completely. would love to get an update if this featrure will be added.
We really need this feature as well, otherwise we simply cant use ecr. I really hope this gets added soon as i would love to use ecr but simply cant add this overhead in our scenario
Please please please make it so! All other repositories have this feature which makes integrations with ECR a bear.
I don't understand how this is so hard, this text is in the beginning of every issue, and is applies to a lot more than just this AWS repo:
Community Note
- Please vote on this issue by adding a 👍 reaction 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
It's very disappointing to get updates as a follower on this issue with yet another person writing pointless comments. Ironically quite a few people that left +1 comments haven't even given a thumbs up so their voice is not even heard.
That will help make the issue more visible when maintainer sort by 👍-reactions, which is what they do..
(example)
If you are truly interested in getting priority bumped for repos that use systems like this just click the good damn 👍 button on the issue (the post at the top) and be happy 😄
Anyway sorry for contributing to the notifications and the rant..
Hi everyone. I apologize for being late to update on this one. We absolutely hear that this is a feature that many customers would like to see. The 'under consideration' tag still applies, and hopefully we provide more updates soon.
By design, ECR has not had create on push as a number of features and configuration options exist for repositories. Settings for these features, from access controls to tag immutability to encryption have a default of 'none', for security reasons. So we need to sort that out before we create repos that aren't useful for most use cases.
Our plan is still to leverage registry-scoped configuration profiles, see #799 . This was the idea a while back and it still makes sense, but we needed to do some initial work in the service. At this point, we're starting to scope this out. I know it's been a while, thanks for your patience and we do hear you.
We'll share more when we have some tangible news to share. Thanks all!
I love AWS in general, but just so you know, this works fine in Google Cloud Container Registry.
@jlbulter Thank you for your detailed response! I appreciate hearing you all are actively working on this issue. Do you think this feature could potentially be released by the end of Q4 2023? No rush at all (workaround in the link below), I was just curious if there are any updates.
For the time being, I will use the suggestion listed: https://stackoverflow.com/questions/51028677/create-aws-ecr-repository-if-it-doesnt-exist
Thank you again for your time, @skchronicles
Hi All, we are working on this. We'll provide an update on the progress at a later date.
May I suggest this should work in combination with the new repository templates feature?
To be clear now repository templates works only when it's AWS automation that are creating the repo. E.g. A pull through cache repo is created automatically (when the corresponding image is pulled by a client) and the template is applied.
However the template does not apply when I create a repo manually with the cli
