-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: replace docker pull push with skopeo #178
Conversation
8fb229b
to
b4d6cbe
Compare
629de02
to
d7bdb54
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I think you should explicit some information about this PR, for example using this PR template.
BTW, isn't this PR rather a refactor than a feat ?
ffcc063
to
4cc93f7
Compare
If you need to ensure an image is actually uploaded before being used, you should add a dependency on skopeo2_copy on the output |
83538d0
to
14365ec
Compare
37530f6
to
5cbe4d6
Compare
@@ -3,7 +3,6 @@ variable "aws_profile" { | |||
description = "AWS Profile used to login and push container images on ECR" | |||
type = string | |||
} | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can revert this
e16a4fd
to
a33f2e3
Compare
Update container-registry/aws/ecr/main.tf Co-authored-by: lemaitre-aneo <[email protected]>
Update container-registry/aws/ecr/main.tf Co-authored-by: lemaitre-aneo <[email protected]>
e4a4fc1
to
b83d6e0
Compare
b83d6e0
to
b173395
Compare
There are many calls for Docker pull and push to populate an internal ECR on AWS.
We suggest using Scope, a client that helps avoid this approach and simplifies the process by cloning images from a source to a target.