-
Notifications
You must be signed in to change notification settings - Fork 147
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
Using rolling release of EC #1842
Conversation
We pinned to a specific release in #1788, because the |
We got it fixed here. enterprise-contract/ec-cli#2244. Without regular updates of the cli, it can fall behind the policies which can cause issues. |
@chmeliik I'm going to add an additional verification step to help prevent this also. https://issues.redhat.com/browse/EC-1082 |
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.
Assuming more robust releases of ec-cli this LGTM
Since there's not an easy way to update ec use the rolling release. This copies the ec binary from the ec-cli image instead of downloading it from Github. https://issues.redhat.com/browse/EC-1066
c803edd
to
727715d
Compare
@chmeliik I misunderstood the issue. It was with the Github release process and not with the ec-cli image. This latest change copies the binary from the ec-cli image bypassing the download from Github. The verification step after the image is built is also added. https://github.com/enterprise-contract/ec-cli/pull/2280/files |
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.
Nice, this seems better 👍
Since there's not an easy way to update ec use the rolling release.
https://issues.redhat.com/browse/EC-1066