Fix checksum command to strictly follow the required format + remove quiet option not supported in BusyBox implementation #46
Conversation
This file contains hidden or 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
…quiet option not support in BusyBox implementation
nikita-tkachenko-datadog
changed the title
ManuelPalenzuelaDD
approved these changes
Jul 30, 2025
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 does this PR do?
Fixes the format of
sha256sumcommand input: strict validation requires that there are 2 spaces between the checksum and the filename, so depending on the command version the previous call with only 1 space could fail.Removes the
--quiteoption from the checksum command, as thesha256sumversion that comes with BusyBox does not support it.Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes