commit | 5b7f5cd768fda3604c657396f738064dbbed2463 | [log] [tgz] |
---|---|---|
author | Jason Peterson <jasonpet@us.ibm.com> | Tue Nov 08 13:39:05 2016 -0500 |
committer | Jason Peterson <jasonpet@us.ibm.com> | Tue Nov 29 10:27:17 2016 -0500 |
tree | 395798dc03cdab0ca5802350baf906b4da4c3cab | |
parent | b8b7bf69c2b2a0c96d03c093e6e3f310365397e8 [diff] |
Add test infrastructure for cloudant
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.