style95 commented on issue #486:
URL: https://github.com/apache/openwhisk-cli/issues/486#issuecomment-1976027871

   Have you tried with the CLI 1.2.0?
   
   https://github.com/apache/openwhisk-cli/releases/tag/1.2.0
   
   Are you able to run the `wsk` cli itself or des it exit?
   
   ```bash
   macbook16:OpenWhisk_CLI-1.2.0-mac-amd64 style95$ ./wsk
   
           ____      ___                   _    _ _     _     _
          /\   \    / _ \ _ __   ___ _ __ | |  | | |__ (_)___| | __
     /\  /__\   \  | | | | '_ \ / _ \ '_ \| |  | | '_ \| / __| |/ /
    /  \____ \  /  | |_| | |_) |  __/ | | | |/\| | | | | \__ \   <
    \   \  /  \/    \___/| .__/ \___|_| |_|__/\__|_| |_|_|___/_|\_\
     \___\/ tm           |_|
   
   Usage:
     wsk [command]
   
   Available Commands:
     action      work with actions
     activation  work with activations
     api         work with APIs
     help        Help about any command
     list        list entities in the current namespace
     namespace   work with namespaces
     package     work with packages
     project     The OpenWhisk Project Management Tool
     property    work with whisk properties
     rule        work with rules
     sdk         work with the sdk
     trigger     work with triggers
   
   Flags:
         --apihost HOST         whisk API HOST
         --apiversion VERSION   whisk API VERSION
     -u, --auth KEY             authorization KEY
         --cert string          client cert
     -d, --debug                debug level output
     -h, --help                 help for wsk
     -i, --insecure             bypass certificate checking
         --key string           client key
     -v, --verbose              verbose output
   
   Use "wsk [command] --help" for more information about a command.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to