Fix checksum checks for cri-tools #258
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Marko Mudrinić <[email protected]>
kubermatic-bot
added
docs/none
|
LGTM label has been added. Git tree hash: fe28177630ff3d073d50d810d06bf2ce5adf743f
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmedwaleedmalik, xmudrii The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubermatic-bot
added
the
approved
xmudrii
added a commit
to xmudrii/operating-system-manager
that referenced
this pull request
Jan 24, 2023
Signed-off-by: Marko Mudrinić <[email protected]> Signed-off-by: Marko Mudrinić <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
cri-tools changed the format of their checksums file. Previously, they had
<checksum> */<filename>. This was breakingsha256sumso we had to do some magic to fix it.Nowadays, they just provide the checksum (
<checksum>), which also breakssha256sumso we need to adjust our magic just a little bit.What type of PR is this?
/kind cleanup
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: