Thanks to both of you for the information. I’m good with using $HOME instead and will document such for my customers.
-Stephen > On Jul 31, 2016, at 4:03 PM, Clayton Coleman <[email protected]> wrote: > > Since this is a problem with she'll expansion itself, the recommendation > (answer we've given before) is to use $HOME > > On Jul 31, 2016, at 3:38 PM, Jordan Liggitt <[email protected]> wrote: > >> Shell expansion doesn't work in the middle of a value... it means we have to >> special-case ~ inside the command logic itself, which is unfortunate >> >> Feel free to open an issue at https://github.com/openshift/origin/issues/new >> >> I'm sure this isn't the only filepath handling code that has this issue. >> It's questionable how far we want to go to duplicate shell expansion inside >> commands, though >> >> >> >> >> On Sun, Jul 31, 2016 at 3:25 PM, Braswell, Stephen <[email protected]> wrote: >> Hello, >> >> Recently when trying to add a new secret, I noticed that the ‘oc’ command >> doesn’t seem to support tilde expansion for home directory location. For >> example, I tried to run the following: >> >> oc secrets new-sshauth mysecret --ssh-privatekey=~/.ssh/openshift_rsa >> >> and got a no such file error: >> >> error: open ~/.ssh/openshift_rsa: no such file or directory >> >> If I point to the actual full path it works. I’ve tried this on both Mac >> and RHEL 7. Here is the version of the ‘oc’ command I’m using (from >> Enterprise/Container Platform): >> >> oc v3.2.1.9-1-g2265530 >> kubernetes v1.2.0-36-g4a3f9c5 >> >> >> Thanks, >> >> -Stephen >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
