| commit | 0962ab5c0a5365bed26a88ff4e46f6f6efb75450 | [log] [tgz] |
|---|---|---|
| author | Nick M. Mitchell <nickm@us.ibm.com> | Tue Oct 04 13:51:01 2016 -0400 |
| committer | Nick M. Mitchell <nickm@us.ibm.com> | Tue Oct 04 13:51:01 2016 -0400 |
| tree | aeb79a8ae31bfb2099fc0d17b30847bd9eca707c | |
| parent | ae2e3f77563e6e78298ded676b9f63ac6bd9565a [diff] |
argv parsing
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