This is an automated email from the ASF dual-hosted git repository.
csantanapr pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-openwhisk.git
The following commit(s) were added to refs/heads/master by this push:
new 1434b21 Vagrant documentation improvement (#4120)
1434b21 is described below
commit 1434b21a85a1fb19214d33e36fb89e1bb059bf10
Author: atsag <[email protected]>
AuthorDate: Mon Nov 19 23:19:41 2018 +0200
Vagrant documentation improvement (#4120)
* Added link to wsk client binaries as these are not built for Windows, and
added appropriate Windows Powershell code to correctly handle nested commands
in Windows systems
* Replaced references to compiled wsk binaries for Windows and MacOS with
suitable downloads, refined commands to properly accommodate Windows Powershell
---
tools/vagrant/README.md | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/tools/vagrant/README.md b/tools/vagrant/README.md
index 1dce73d..6340132 100644
--- a/tools/vagrant/README.md
+++ b/tools/vagrant/README.md
@@ -101,7 +101,10 @@ same IP address.
The CLI is available in `../../bin`.
The CLI `../../bin/wsk` is for Linux amd64.
-The CLI for other operating systems and architectures can be found under
`../../bin/openwhisk-cli/build/`
+The CLI for all other operating systems and architectures (as well as Linux)
can be
+downloaded in a compressed format from
[https://github.com/apache/incubator-openwhisk-cli/releases](https://github.com/apache/incubator-openwhisk-cli/releases)
.
+For more details, please consult the relevant
[documentation](https://openwhisk.apache.org/documentation.html) section
"Download and
+install the wsk CLI from (Linux, Mac or Windows):".
When using the CLI with a local deployment of OpenWhisk (which provides an
insecure/self-signed SSL certificate), you must use the argument `-i` to permit
@@ -113,10 +116,12 @@ location of the binary that corresponds to your
environment.
From your _host_, configure `wsk` to use your Vagrant-hosted OpenWhisk
deployment and run the "echo" action again to test. The following commands
-assume that you have `wsk` setup correctly in your PATH.
+assume that you have `wsk` setup correctly in your PATH (and that you are using
+Powershell if your deployment is hosted in Windows).
```
# Set your OpenWhisk Authorization Key.
-wsk property set --apihost 192.168.33.16 --auth `vagrant ssh -- cat
openwhisk/ansible/files/auth.guest`
+
+wsk property set --apihost 192.168.33.16 --auth $(vagrant ssh -- cat
openwhisk/ansible/files/auth.guest)
# Run the hello sample action
wsk -i action invoke /whisk.system/utils/echo -p message hello --result
@@ -131,7 +136,7 @@ Vagrant installation is self-signed. Alternatively, you can
configure your
_apihost_ to use the non-SSL interface:
```
-wsk property set --apihost http://192.168.33.16:10001 --auth `vagrant ssh --
cat openwhisk/ansible/files/auth.guest`
+wsk property set --apihost http://192.168.33.16:10001 --auth $(vagrant ssh --
cat openwhisk/ansible/files/auth.guest)
```
You do not need to use the `-i` switch to `wsk` now. Note, however, that `wsk
