serverless-architectures
Here are 177 public repositories matching this topic...
-
Updated
Dec 15, 2021 - Go
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-
-
Updated
Apr 25, 2022 - TypeScript
-
Updated
Oct 29, 2021
-
Updated
Apr 9, 2022 - JavaScript
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
JSON support
-
Updated
Apr 21, 2022 - Go
-
Updated
Jun 21, 2019 - TypeScript
-
Updated
Dec 14, 2021
-
Updated
Jun 24, 2018 - Shell
-
Updated
Apr 11, 2022 - C#
-
Updated
Aug 11, 2021 - JavaScript
-
Updated
Mar 8, 2022 - Shell
-
Updated
Oct 23, 2019 - JavaScript
The interceptor should be able to route requests for the same host to different services based on the request path.
Use-Case
When using an ingress controller, you can create Ingress objects that route different requests for the same host to different backend services, depending on the path portion of the request. This can be done by within a single Ingress object or across multiple of
-
Updated
Apr 11, 2022 - JavaScript
-
Updated
Apr 25, 2022 - TypeScript
-
Updated
Apr 30, 2020 - JavaScript
-
Updated
Feb 23, 2019 - Go
-
Updated
Oct 1, 2020 - JavaScript
Loop detection
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
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.
-
Updated
Apr 12, 2022 - C#
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.
-
Updated
Mar 11, 2022 - Python
-
Updated
May 20, 2017
Expected behavior:
Serve static Files with cors enabled. No cors headers present.
Actual behavior:
Cors error:
Access to XMLHttpRequest at 'https://[URL]' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Steps to reproduce the problem:
Serve the static file:
event.pa
-
Updated
Mar 12, 2019 - HCL
Improve this page
Add a description, image, and links to the serverless-architectures topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the serverless-architectures topic, visit your repo's landing page and select "manage topics."


Is there an existing issue for this?
Use case description
Currently, we have websocket-related properties configured directly on
providerlevel:provider.websocketsApiNameprovider.websocketsApiRouteSelectionExpressionprovider.websocketsDescriptionThis is not consistent with how
iam,httpApior