Use case description

AWS recently announced support for Amazon MQ as an event source for AWS Lambda. Reference article: https://aws.amazon.com/blogs/compute/using-amazon-mq-as-an-event-source-for-aws-lambda/

Proposed solution

Introduce a new event type, mq, that will allow to use Amazon MQ as an event source for functions defined with Serverless Framework. General implementati

The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.

We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.

Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-

Is your feature request related to a problem? Please describe.

支持自动检测框架的覆盖范围仅仅支持了几个常见前端框架和函数，还可以拓展更多的框架和语言来提升体验

这块的实现是基于配置式的，可以比较轻松拓展一个新框架的支持
https://github.com/TencentCloudBase/cloudbase-framework/blob/master/packages/framework-core/src/detect-frameworks/frameworks.ts

大家可以通过这个快速参与进核心代码的开发当中，目前可以考虑支持的框架和技术有 Hexo, Egg, Koa, Express, Koa , Docker 容器等

• Vue
• React
• V

synk report issue

Description

We are synk (https://snyk.io/) for checking used packages.

Synk is complaining about a security issue for serverless-step-functions.
https://snyk.io/vuln/SNYK-JS-DOTPROP-543489

Additional Data

• Serverless Framework Core Version you're using: 1.64.1
• The Plugin Version you're using: 2.17.1
• Operating System: macOS Majove 10.14

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.

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.

I don't think it's a necessary requirement that the main function in a zip action is located in the file index.php. If we adopt the aws lambda convention of path/to/file.handler then it's possible to locate the "index" anywhere in the zip and this is an added convenience particularly working with existing php code.