commit | 6da0aca454a1154914e57eb1e289e045807e8899 | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Tue Oct 04 14:30:26 2016 -0400 |
committer | Nick M. Mitchell <nickm@us.ibm.com> | Tue Oct 04 14:30:26 2016 -0400 |
tree | f7a192c0d623cd46d05f75d4ae19467493e6419a | |
parent | e0437b0ac557b65d083134a2192a55e78216db0b [diff] |
fix support for --use-cli-debugger
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