commit | ee733d9c060e783a35b2c3f623b40a8a28b6902f | [log] [tgz] |
---|---|---|
author | Morgan Johnson <johnsolm@us.ibm.com> | Fri Dec 09 14:15:01 2016 -0500 |
committer | Morgan Johnson <johnsolm@us.ibm.com> | Fri Dec 09 14:15:01 2016 -0500 |
tree | d725336f751015d03cb239ab52284ca432c15df1 | |
parent | be2ae7a70cb9a3001f3443478080594dcf6ba794 [diff] |
updating class name spec for the trigger persistency
This is still very much a work-in-progress.
RESTful service to listen for changes to a Cloudant database.
Changes to a Cloudant database can trigger the invocation of an action, passing the action the body of the updated document.
See the scripts directory for examples on how to register a new Cloudant trigger.
The following commands will test the Cloudant trigger service:
cd <bluewhisk_home> gradle distDocker
Follow the instructions in [ansible/README.md][../../../ansible/README.md]
./bin/wsk create HELLOCLOUDANT ./actions/hellocloudant.js ./catalog/providers/cloudantTrigger/scripts/addTestTriggers.sh
./catalog/providers/cloudantTrigger/scripts/addNewDocument.sh
You should see the output from invoking the HELLOCLOUDANT action in the ELK logs.