Google Git
Sign in
apache / openwhisk-package-cloudant / 9e43965e84c043552ebe2070d1db21807f704033
commit9e43965e84c043552ebe2070d1db21807f704033[log] [tgz]
authorJason Peterson <jasonpet@us.ibm.com>Tue Nov 01 22:19:23 2016 -0400
committerJason Peterson <jasonpet@us.ibm.com>Tue Nov 01 22:19:23 2016 -0400
tree81adfc96c6ce6c6cd3e6ef036fadf0ec8e17e2cf
parent391235b009e4191a5809dfe9165722df05202752 [diff]
fix for empty dockerRegistry property
1 file changed
tree: 81adfc96c6ce6c6cd3e6ef036fadf0ec8e17e2cf
  1. actions/
  2. gradle/
  3. lib/
  4. scripts/
  5. .gitignore
  6. app.js
  7. build.gradle
  8. Dockerfile
  9. gradlew
  10. gradlew.bat
  11. installCatalog.sh
  12. Logger.js
  13. package.json
  14. 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.