commit | b8f747a2c36bf0ef64adbf6906207550c482eb63 | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 19:59:59 2016 -0400 |
committer | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 19:59:59 2016 -0400 |
tree | 0b702506e58f856d1246e141a733c5cc4e5bc7ce | |
parent | ab3144d26676b786041301c8eebe2b1cf20b1c74 [diff] |
use a fork of Inquirer that lets us get rid of the question mark prefix
This project currently supports debugging NodeJS actions on your laptop.
Start the debug client:
% (cd client; ./wskdb) Welcome to the OpenWhisk Debugger ? (wskdb)
You will now be in a REPL. Issue help
to see the list of available commands.
The syntax here is almost identical to that of the wsk
CLI.
? (wskdb) invoke actionName -p param1 value1 -p param2 value2
If you haven‘t yet attached to the action you are invoking, the invocation will proceed as if you weren’t in the debugger, and had issued a blocking invocation from the CLI.
Say for example you wish to attach to an action foo
, and this action occurs in a sequence seq
.
(wskdb) attach foo Attaching to foo Creating action trampoline Creating sequence splice seq
If you wish to limit the instrumentation to the action, avoiding any containing rules or sequences:
(wskdb) attach foo --action-only Attaching to foo Creating action trampoline