Google Git
Sign in
apache / openwhisk-package-cloudant / b11e386664f4adec7a931680d502036aa33c6c17
commitb11e386664f4adec7a931680d502036aa33c6c17[log] [tgz]
authorCarlos Santana <csantana23@gmail.com>Thu Feb 02 10:26:12 2017 -0500
committerGitHub <noreply@github.com>Thu Feb 02 10:26:12 2017 -0500
treebf163209ddadc170838ca51b9a5d8432cbe67688
parent53e99be02970d418c06bcb2f3ab9772ef098e536 [diff]
parent7f948942600043831621c9611cb9d9f240535b62 [diff]
Merge pull request #58 from jasonpet/scancode

Add travis scancode support
tree: bf163209ddadc170838ca51b9a5d8432cbe67688
  1. actions/
  2. gradle/
  3. provider/
  4. tests/
  5. tools/
  6. .gitignore
  7. .travis.yml
  8. build.gradle
  9. CONTRIBUTING.md
  10. Dockerfile
  11. gradlew
  12. gradlew.bat
  13. installCatalog.sh
  14. package.json
  15. README.md
  16. 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.