Update Linux installation process on README to have a way to dynamically get kubeseal version number #1294
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
… in install Signed-off-by: Alex Yong <[email protected]>
…nstall docs: updating readme to show how to get kubeseal version dynamically…
alexjyong
requested review from
alvneiayu,
agarcia-oss and
alemorcuq
as code owners
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.
Description of the change
Updating the README.md to show how to get the version of kubeseal dynamically instead of having to hardcode it for the Linux install script
Benefits
Users don't have to go to the release page to find the latest version
Install script can be used in CI/CD environments or other environments where kubeseal may be dynamically installed and this will allow the version of the latest to be automatically installed
Possible drawbacks
Adds extra detail to the README. I've maintained the original way to do it in the event the user using this doesn't have
jqandcurlinstalled, which is required for this method and cannot/does not want to install it.Applicable issues
N/A
Additional information
N/A