commit | a1a0f707c1d01a95f4095402668e20e08c6022e0 | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 18:32:36 2016 -0400 |
committer | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 18:32:36 2016 -0400 |
tree | 800157eb0a9d6565d6183290f1bccc11acc1e920 | |
parent | fe39e19b52a0b7078167d9b942ce446095b640ca [diff] |
update the debug-bootstrap to console.log the return value
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