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.

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

The annotation value require-whisk-auth: false on a web action leads the controller to reject the web action invocation.

1. The openwhisk documentation does not say what should happen when the value is false. I don't know why this case is omitted case https://github.com/apache/openwhisk/blob/master/docs/webactions.md#securing-web-actions
2. The implementation treats this case as "not allowed

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

It looks like the list with extensions on the website is incomplete. Just deployed a microservice running bref using ext-gd even though there is no mention of it here: https://bref.sh/docs/environment/php.html#extensions-installed-and-enabled

Hi,

I wanted to enable binary support on API gateway, but could not find the way to do it via component's inputs.

Is this something that you would consider adding in the future?

If so, I can try to add this feature. It doesn't look too complicated.

Thanks!

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

fx access HTTP endpoint of docker engine to do image build and container run, but currently fx make docker endpoint to support HTTP with "socat" with docker run https://github.com/metrue/fx/blob/master/provisioner/darwin/darwin.go#L18, it'd would be great to migrate it to Go.

Reliability monitoring - e2e testing of GitHub workflow

Context

Since moving the Communtity Cluster from GKE to DigitalOcean the reliability has dropped dramatically due to issues with the Cilium networking driver 1.4.0. A separate action will be required for this, but in the meantime it highlights a lack of e2e monito

There is some old Jenkinsfile Runner code which was originally a part of Jenkins test frameworks. This code uses the "Hudson" name though Jenkins was renamed to Hudson in 2011. It would be great to cleanup this code. Some occurences: https://github.com/jenkinsci/jenkinsfile-runner/search?q=Hudson

Acceptance criteria:

• "Hudson" occurrences in the documentation, Javadoc and comments are repla

Expected Behaviour

We should prepare Derek for use as an SDK/package so that he can be run on any platform - a Go microservice, AWS Lambda, Heroku etc.

This is the first ste

Can't have "template" folder in function folder

Expected Behaviour

This function stopped working at this commit, renaming template to templates fixed the issue

https://gi

Description

We need a volunteer to update all the guides, terraform automation and cloud-config.txt to use the release 0.9.0

The assets are in this repo, so you shouldn't have too hard of a time finding stuff. Bear in mind we now have a dependency on docker-compose.yaml and that may need to be downloaded before faasd install.

Feel free to ask questions here.

The new cloud-config.t

Feature Request

Add a --context flag to dispatch CLI.

Detailed Description

You can have multiple contexts in the dispatch config file (~/.dispatch/config.json). Each context stores the location of a dispatch endpoint. Currently, to switch context you need to do `dispatch manage context --set <context_