functions-as-a-service

Is your feature request related to a problem? Please describe.
Currently, there are two ways to create HTTPTrigger using the fission command.

1. fission fn create with below parameters

  --url=''                              URL pattern (See gorilla/mux supported patterns)
  --prefix=''                           Prefix with which functions are exposed. NOTE: Prefix takes
    

Environment details:

• local deployment (standalone openwhisk)

Steps to reproduce the issue:

1. create a web action using this function:

> cat t.js
const main = () => ({
  "body": {
    "message": "hello"
  },
  "statusCode": 442
})

2. invoke the web action

> wsk action update t t.js --web true
> curl -X POST `wsk action get t --url`
{
  "code": "b86c3c

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the APIHOST variable as https://localhost:8443/ in the config file, with the trailing slash, which causes 404s since the CLI was sending requests to https://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0 (n

The test does not gracefully remove the minio server. Once it is added, it should be re-enabled.

In this PR: apache/openwhisk-wskdeploy#1124

I updated all the dependencies to their latest versions, but go-18n has a new v2 interface which can be explored for adoption and hopefully in the process improve the methods by which we generate the i18n_resources.go file and language resources.

currently you have to run composer twice, once to generate the function code and again to generate the ast (needed for k/o-ui visualization).

it would be convenient to run compose once and specify two different files for output.

Add logic to detect when an API might be calling itself (directly or via another API) in a loop, and terminate the loop.

This can be done through injection of unique headers for every hop through the gateway.

For example:

Client request -> GW: GET /api1
GW inject header: X-ApiGw-Loop: get_api1
GW request -> GW: GET /api2
GW inject header: X-ApiGw-Loop: get_api1 get_api2
GW req

If the npm package that is defined by https://github.com/apache/incubator-openwhisk-runtime-nodejs/blob/master/core/nodejs8Action/package.json was published to npm then projects would be able to depend on it and get the current set of js dependencies present in OW. Those projects building with webpack would also be able to exclude those packages from their builds, making their images smaller.