-
Notifications
You must be signed in to change notification settings - Fork 555
Use command as quoted string in CloudAuth #352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use command as quoted string in CloudAuth #352
Conversation
Welcome @jnummelin! |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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/test-infra repository. I understand the commands that are listed here. |
441767a
to
ca523c1
Compare
Thanks for this! I remember dealing with something similar with windows pathing previously too #238 it seems like this is a constant problem of back and forth. So your idea of adding a test case for this I believe would solve it hopefully once and for all.
We support windows so doing a But what about potentially trying one of these 2 options(just ideas).
How does that sound? |
We use |
@drubin Thanks for the ideas. I implemented the test case with option 1, with a small js script named |
/lgtm Thanks for the PR! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, jnummelin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We faced a case where
gcloud
for some reason was installed in path that contains whitespaces. This results in slightly weird (but still perfectly working[1]) kubeconfig:Now as the
CloudAuth
uses plainchild_process
for exec it naturally breaks in this case.It used to work with 0.10.2 version, but seems 0055a50 broke it when
CloudAuth
was changed to use plainchild_process
.I'd appreciate some pointers and ideas how to make the test case actually portable and without any need to manually first create symlinks. Would it make sense to dynamically create a symlink to
echo
in some temp dir with whitespaces in the name?[1]
kubectl
works perfectly still, so did previous version of JS client as it usedexeca