Google Git
Sign in
apache / openwhisk-package-cloudant / 53e99be02970d418c06bcb2f3ab9772ef098e536
commit53e99be02970d418c06bcb2f3ab9772ef098e536[log] [tgz]
authorMatt Rutkowski <mrutkows@us.ibm.com>Wed Jan 25 10:30:30 2017 -0600
committerGitHub <noreply@github.com>Wed Jan 25 10:30:30 2017 -0600
tree54b93669092199ad84f669e8523b08cdf0d643d2
parentdfc99f655f5810a0b98f62f0f7e967ad0d43d4ba [diff]
Create CONTRIBUTING.md
1 file changed
tree: 54b93669092199ad84f669e8523b08cdf0d643d2
  1. actions/
  2. gradle/
  3. provider/
  4. tests/
  5. .gitignore
  6. build.gradle
  7. CONTRIBUTING.md
  8. Dockerfile
  9. gradlew
  10. gradlew.bat
  11. installCatalog.sh
  12. package.json
  13. README.md
  14. settings.gradle
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.