Return an error instead of panicking on a valueless mount option - #2271
arpitjain099 wants to merge 1 commit into
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
|
Welcome @arpitjain099! It looks like this is your first PR to knative/client 🎉 |
|
Hi @arpitjain099. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arpitjain099 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Description
kn service create foo --image ... --mount /mydir=ed:ed1:readOnlypanics withindex out of range [1] with length 1.parseMountOptionssplits each option on=and readspair[1]for thereadonlycase without checking that the split produced two elements, so leaving off the value crashes the CLI instead of printing a usage error. The flag help documentsreadOnly=true | false, so a barereadOnlyis a plausible typo.While in there I removed a leftover in
getMountInfo: it splits the option string and runs aswitchwhose only case is empty, then ignores the result. It has no effect.Changes
readonlymount option with no value and return an error naming the optiongetMountInforeadonly=true,readonly=false,readonly=, barereadonlyand an unknown optionReference
Fixes #
Release Note