commit | a6421d43db4ede03ac18cbce40eed7b8e78586e3 | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Thu Sep 29 21:55:40 2016 -0400 |
committer | GitHub Enterprise <noreply@github.ibm.com> | Thu Sep 29 21:55:40 2016 -0400 |
tree | 448f6cd150dc7ac6f261f29699aed35181a5ca28 | |
parent | 446160bb41ce8159741fdbedd353628667e38056 [diff] |
Update README.md
This project currently supports debugging NodeJS actions on your laptop.
First, for now, you will need to get the invoker action into your namespace:
% (cd invoker; ./init.sh)
Next, 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