Ricardo Oliveira
Ricardo Oliveira
Probably because the most common case is that people want to ignore ESI... It could be configurable though - try submitting a PR for it if you still need it...
given the required changes in the AWS SDK has been merged, what needs to happen on this side to fulfil this feature request?
Hi @bgreg1012 , thanks for opening this - any chance you could look into the tests as mentioned by @osterman?
I'm seeing the same thing here
:+1: failing here too
Indeed, I've seen this same behaviour more than a year later, using version 1.0.0 of this provider
now that https://aws.amazon.com/about-aws/whats-new/2019/01/aws-fargate--amazon-ecs--and-amazon-ecr-now-have-support-for-aws/ has been released, the need for this issue would only relate to using private repositories other than ECR
> > so this issue is only relevant for people wishing to use private repositories other than ECR. > > Correct me if I'm mistaken but this also prevents pulling...