place the multicall links in $PATH - #4867
Closed
joshrwolf wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Josh Wolf <josh@wolfs.io>
Member
Author
|
nevermind, this means |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
the packaged multicalls were previously in the k3s
datadir, which were unpacked into/var/lib/rancher/k3s/data.this change places them instead directly in
/bin/$i, so that callers can access them directly without adjusting their $PATH.worth noting that accessing them via the outer
k3s(k3s kubectl ...) will still work