I am using the new support for EFS. Another stack outputs the ARN of the EFS and I use it as follows

functions:
  myLambda:
    handler: src/main.something
    fileSystemConfig:
      localMountPath: /mnt/efs
      arn:
        'Fn::ImportValue': ${self:custom.stage}-my-efs-access-point-arn

While this works, it throws the following warning during deploy:

Serverless:

Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Is your feature request related to a problem? Please describe.
It would be great to be able to configure the route output, e.g. I want to hide the Cube.js server is running in production mode. Learn more about production mode. when the base route is hit

Describe the solution you'd like
I think it would be great if one could configure the output of https://github.com/cube-js/cube.js/

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

/area operator

Ops are not loving the idea of giving dapr-operator cluster-admin permissions. Is this really necessary and if so, what is it necessary for (i.e. what operations does it have to do where more restrictive permissions would not suffice)?

Thanks!

Kubectl explains is useful for a Fission user to write function specs especially but it does not give any information as of now.

$ kubectl explain functions -ndefault
KIND:     Function
VERSION:  fission.io/v1

DESCRIPTION:
     <empty>

It should look something similar to:

$ kubectl explain pod.spec
KIND:     Pod
VERSION:  v1

RESOURCE: spec <Object>

DESCRIPTION

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-

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

https://emotion.sh/

After this change in Material UI: mui-org/material-ui#6115