Add use() method to short-circuit requests with no route handlers (#113)

* Fix Node Express 'use()' method by removing invalid 'err' parameter

* Add use() method to short-circuit requests with no handlers

* Add use() method to short-circuit requests with no handlers
2 files changed
tree: b6f11dc61c9394ec1ebd075adee1dcc639133caf
  1. .github/
  2. core/
  3. gradle/
  4. tests/
  5. tools/
  6. .gitattributes
  7. .gitignore
  8. .scalafmt.conf
  9. .travis.yml
  10. build.gradle
  11. CONTRIBUTING.md
  12. DISCLAIMER.txt
  13. gradlew
  14. gradlew.bat
  15. LICENSE.txt
  16. NOTICE.txt
  17. README.md
  18. settings.gradle
README.md

Apache OpenWhisk runtimes for nodejs

License Build Status

Give it a try today

To use as a docker action for Node.js 6

wsk action update myAction myAction.js --docker openwhisk/nodejs6action

To use as a docker action for Node.js 8

wsk action update myAction myAction.js --docker openwhisk/action-nodejs-v8

This works on any deployment of Apache OpenWhisk

To use on deployment that contains the runtime as a kind

To use as a kind action using Node.js 6

wsk action update myAction myAction.js --kind nodejs:6

To use as a kind action using Node.js 8

wsk action update myAction myAction.js --kind nodejs:8

Local development

For Node.js 6

./gradlew core:nodejs6Action:distDocker

This will produce the image whisk/nodejs6action

For Node.js 8

./gradlew core:nodejs8Action:distDocker

This will produce the image whisk/action-nodejs-v8

For Node.js 10

./gradlew core:nodejs10Action:distDocker

This will produce the image whisk/action-nodejs-v10

Build and Push image for Node.js 6

docker login
./gradlew core:nodejs6Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io

Build and Push image for Node.js 8

docker login
./gradlew core:nodejs8Action:distDocker -PdockerImagePrefix=$prefix-user -PdockerRegistry=docker.io

Then create the action using your image from dockerhub

wsk action update myAction myAction.js --docker $user_prefix/nodejs6action

The $user_prefix is usually your dockerhub user id.

Deploy OpenWhisk using ansible environment that contains the kind nodejs:6 and nodejs:8 Assuming you have OpenWhisk already deployed locally and OPENWHISK_HOME pointing to root directory of OpenWhisk core repository.

Set ROOTDIR to the root directory of this repository.

Redeploy OpenWhisk

cd $OPENWHISK_HOME/ansible
ANSIBLE_CMD="ansible-playbook -i ${ROOTDIR}/ansible/environments/local"
$ANSIBLE_CMD setup.yml
$ANSIBLE_CMD couchdb.yml
$ANSIBLE_CMD initdb.yml
$ANSIBLE_CMD wipe.yml
$ANSIBLE_CMD openwhisk.yml

Or you can use wskdev and create a soft link to the target ansible environment, for example:

ln -s ${ROOTDIR}/ansible/environments/local ${OPENWHISK_HOME}/ansible/environments/local-nodejs
wskdev fresh -t local-nodejs

Testing

Install dependencies from the root directory on $OPENWHISK_HOME repository

./gradlew install

Using gradle for the ActionContainer tests you need to use a proxy if running on Mac, if Linux then don't use proxy options You can pass the flags -Dhttp.proxyHost=localhost -Dhttp.proxyPort=3128 directly in gradle command. Or save in your $HOME/.gradle/gradle.properties

systemProp.http.proxyHost=localhost
systemProp.http.proxyPort=3128

Using gradle to run all tests

./gradlew :tests:test

Using gradle to run some tests

./gradlew :tests:test --tests *ActionContainerTests*

Using IntelliJ:

  • Import project as gradle project.
  • Make sure working directory is root of the project/repo
  • Add the following Java VM properties in ScalaTests Run Configuration, easiest is to change the Defaults for all ScalaTests to use this VM properties
-Dhttp.proxyHost=localhost
-Dhttp.proxyPort=3128

Disclaimer

Apache OpenWhisk Runtime Node.js is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.