Loading repository data…
Loading repository data…
IBM / repository
Simple demo showing how to write actions in different languages with IBM Cloud Functions. Created for the "Build a cloud native app with Apache OpenWhisk" webinar.
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
Note: This demo application was built in 2016. The concepts are the same, but there are alternative approaches for binding Cloudant to the Cloud Functions environment and another way to use Docker that doesn't require you to store action code in the public Docker Hub.
Simple demo showing IBM Cloud Functions (powered by Apache OpenWhisk) programming with actions, triggers, and rules. Created for the Build a cloud native app with Apache OpenWhisk webinar.
This example shows how to write actions in both JavaScript and Docker, respond to database triggers, and invoke actions in a workflow asynchronously.
When an image is added to a Cloudant database, this event triggers the JavaScript action to download the file and resize it. It also invokes an optical character recognition (OCR) library packaged as an action in Docker.
process-check.jsThis action is invoked by the new-check-deposit trigger, which fires when an image of a check is added to a Cloudant database (named incoming-checks). The action downloads the image, invokes the parse-image.sh action to extract account information, resizes the image, then stores a copy back in another Cloudant database (named processed-checks) along with the account data.
parse-image.shThis action is invoked by the process-check.js action above. The action downloads the original check image, parses it for account and routing number data, then returns that to the calling action which in turn stores it in the database.
There is a convenience script for creating and destroying the actions, triggers, and rules. It retrieves configuration information from a local.env file that is created from template.local.env.
After you've installed the wsk binary, created a Cloudant service instance, and installed Docker for your platform, the script can then be used to set up, tear down, and inspect the current configuration:
./deploy.sh --install
./deploy.sh --uninstall
./deploy.sh --env
wsk CLI from BluemixAfter registering for the IBM Cloud, navigate to the "Functions" section. You'll find it in the left navigation, under the three horizontal bar (hamburger) icon.
Click the "Download CLI" button and place the wsk binary in your path, such as in ~/bin. Open a terminal and set your namespace and authorization as shown in step 2. Then create your first action in step 3 to validate your setup.
Under the "Services" option in the left navigation, choose "Data & Analytics", then view the Services portfolio and provision an instance of Cloudant. Save the "Service Credentials" information to local.env and launch the dashboard.
In the Cloudant dashboard, create two databases: incoming-checks and processed-checks.
The deploy.sh script assumes that you have Docker in your path and that you have a Docker Hub account. Install Docker for your platform and sign up for a Docker Hub account. Enter the credentials in local.env.