-
Notifications
You must be signed in to change notification settings - Fork 278
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
update-strategy digest fails with amazon ECR api? #217
Comments
@jannfis Ok so it turns out this works fine. The problem is that on the repo I was testing with, no one was uploading a |
Thanks for the follow-up on this @diranged. So if I understood you correctly, the bug is like:
Is that a correct assumption? If yes, it's definitely a bug :) |
Yup that's basically what happened.. confused the hell out of me! :) |
Thank you @diranged ! I could successfully reproduce the bug, a fix is underway. |
Describe the bug
I'm trying to get around #216 by using the new "digest" update strategy (#176). We're using AWS ECR as our backend and we set the appropriate tags on our image. It seems that the digest mode is set (based on the "setting dummy ..." line in the logs), but something is going wrong with populating the image digest of the latest
latest
image. Here are the logs (I've shared this with @jannfis on Slack privately, but I felt like I should open a bug report here):To Reproduce
Set up an AWS ECR repository and point the Image Updater to it (see #112 (comment)). Then set your Application annotations up like this:
Expected behavior
As soon as it discovers that
latest
is a valid tag that matches ourimage-list
, I expect it to update the Application with thesha256:...
hash of that tag. Instead it is setting it tolatest
which does not trigger a new deploy.Version
Latest master build as of 1d19e6a
The text was updated successfully, but these errors were encountered: