Google Git
Sign in
apache / openwhisk-package-cloudant / b5529958a1f5e63ef12957001a0735cdee6f3e9d
commitb5529958a1f5e63ef12957001a0735cdee6f3e9d[log] [tgz]
authorJason Peterson <jasonpet@us.ibm.com>Fri Oct 28 09:51:43 2016 -0400
committerJason Peterson <jasonpet@us.ibm.com>Fri Oct 28 09:51:43 2016 -0400
tree261ddfede451c724e75aa0fc2fecc2f9f24a739f
parent87d857bdcfa65cb31b5c257f730126651487c824 [diff]
add gradle distdocker build support
6 files changed
tree: 261ddfede451c724e75aa0fc2fecc2f9f24a739f
  1. gradle/
  2. lib/
  3. scripts/
  4. .gitignore
  5. app.js
  6. build.gradle
  7. Dockerfile
  8. gradlew
  9. gradlew.bat
  10. Logger.js
  11. package.json
  12. README.md
README.md

Status

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.

Testing the Cloudant trigger service

The following commands will test the Cloudant trigger service:

Build

cd <bluewhisk_home> gradle distDocker

Deploy

Follow the instructions in [ansible/README.md][../../../ansible/README.md]

Register an action and listen for changes to a test Cloudant database.

./bin/wsk create HELLOCLOUDANT ./actions/hellocloudant.js ./catalog/providers/cloudantTrigger/scripts/addTestTriggers.sh

Insert a new document to the test Cloudant database.

./catalog/providers/cloudantTrigger/scripts/addNewDocument.sh

You should see the output from invoking the HELLOCLOUDANT action in the ELK logs.