Skip to content

fix: validate webhook deployment script arguments#4129

Open
immanuwell wants to merge 1 commit into
kubernetes-sigs:masterfrom
immanuwell:fix/webhook-script-arg-parsing
Open

fix: validate webhook deployment script arguments#4129
immanuwell wants to merge 1 commit into
kubernetes-sigs:masterfrom
immanuwell:fix/webhook-script-arg-parsing

Conversation

@immanuwell

Copy link
Copy Markdown

What this PR does / why we need it:

deploy-vsphere-csi-validation-webhook.sh had busted CLI error handling.
Unknown flags tried to run usage like a command, and --namespace with no value died on a bare shift, so the script faceplanted before it even touched the cluster. Kinda rough.

This patch adds a real usage() helper, returns 0 for --help, validates --namespace, and keeps the normal path the same.

Which issue this PR fixes: None

Testing done:

bash -n manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh

Repro with the old script blob from HEAD:
tmp_old=$(mktemp) && git show HEAD:manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh > "$tmp_old" && chmod +x "$tmp_old" && bash "$tmp_old" --bad-flag
old output: usage: command not found

tmp_old=$(mktemp) && git show HEAD:manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh > "$tmp_old" && chmod +x "$tmp_old" && bash -x "$tmp_old" --namespace
old behavior: exits after a bare shift

Repro with this patch:
bash manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh --bad-flag
now prints a clean unknown-option error and usage text

bash manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh --namespace
now prints a clean missing-value error and usage text

bash manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh --help
now exits 0

bash manifests/vanilla/deploy-vsphere-csi-validation-webhook.sh --namespace vmware-system-csi
still follows the normal path, and in this env stops at kubectl not found

Special notes for your reviewer:

No matching issue found, so this is just a tiny paper-cut fix.

Release note:

NONE

@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: immanuwell
Once this PR has been reviewed and has the lgtm label, please assign kolluria for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 4, 2026
@kubernetes-prow

Copy link
Copy Markdown

Welcome @immanuwell!

It looks like this is your first PR to kubernetes-sigs/vsphere-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/vsphere-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow

Copy link
Copy Markdown

Hi @immanuwell. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.

@kubernetes-prow kubernetes-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 4, 2026
@immanuwell

Copy link
Copy Markdown
Author

@divyenpatel @xing-yang please take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant