lambda

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

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

Expected Behaviour

The following should generate a Rancher Rio Service definition:

faas-cli generate --api=services.rio.cattle.io

apiVersion: rio.cat

What would you like to be added:

This error is shown in the stage log. Need to found out and update error format for all error like this

 (%!w(*fmt.wrapError=&{failed to apply:  (signal: killed) 0xc0090b8dc0}))

Why is this needed:

Expected Behaviour

We should have Travis / Go & OpenFaaS GitHub badges in our README.md file just like openfaas/faas openfaas/faas-netes openfaas/faas-cli and etc.

Curren

Hi!

I would like to run some of my lambdas periodically and it seems there is no straightforward way to do that. What I did was I created a ping action, which curls lambda url and thus invokes it.

ping:
	curl https://my.function.url/

This is a hacky solution, but what is the intended way?

Is it possible to add launcher as an action into the scheduler?

<img width="931" a

For example: RequestCtx(ctx, request). We should also add in the ability to react to the <-done signal.