-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
feat: make checksum optional in upgrade validation #16511
Conversation
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.
left one question but otherwise looks good
type ParseConfig struct { | ||
// EnforceChecksum, if true, will cause all downloaded files to be checked against their checksums. | ||
// When false, checksums are not enforced to be present in the url. | ||
EnforceChecksum bool |
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.
if this is true and cosmovisor flag is false, which one takes priority?
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.
Basically, the software-upgrade CLI still requires a checksum for binary unless a flag is passed to disable it.
And cosmovisor by default do not require the software upgrade binary to have a checksum but an env variable can enforce it. When present checksums are always checked.
@Mergifyio backport release/v0.50.x |
✅ Backports have been created
|
(cherry picked from commit 62709ad) # Conflicts: # tools/cosmovisor/go.mod # tools/cosmovisor/go.sum
…16532) Co-authored-by: Julien Robert <[email protected]>
Description
Closes: #10718, ref: #16131 (comment)
Unblocks: #16131
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change