Skip to content
#

Serverless

Serverless architecture refers to apps that depend on third-party services (backend as a service, or BaaS) or custom code (functions as a service, or FaaS). Their goal is to free the developer and operator from managing the server their code runs on.

Here are 6,950 public repositories matching this topic...

JorisPhilipsen
JorisPhilipsen commented Jan 20, 2021

Use case description

I was wondering if it would be possible to add the enabled boolean flag to the API key settings in the serverless.yml file.

Proposed solution

My proposal would be creating something like this:

provider:
  name: aws
  apiKeys:
    - name: ${self:provider.stage}-test-a
      description: Api key test a
      enabled: true
    - name: ${self:provid
cube.js
dapr
jplock
jplock commented Apr 16, 2020

Description:

I'd like to be able to specify the IAM role Path on either a function or globals.

Observed result:

Able to specify Path on a Function or Globals

Expected result:

Path is set on the implicitly created IAM roles

fission
swaroopnuli
swaroopnuli commented Sep 19, 2020

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

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

rabbah
rabbah commented Apr 2, 2020

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-

rdallman
rdallman commented Jun 13, 2018

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

redynasc
redynasc commented Jan 19, 2021

Issue description
all requests on the upstream return 500 When the one node’s domain dns resolution timeout , even if the other node is ok

Environment

apisix version : 1.5
OS: Linux d1-beta-node-0004 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
OpenResty / Nginx version: (cmd: nginx -V or openresty -V)
nginx version: openresty/1.17.8.2
Wikipedia
Wikipedia
You can’t perform that action at this time.