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

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

Expected Behavior

the link to the operator yaml to work on page https://knative.dev/docs/install/knative-with-operators/

Actual Behavior

404

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!

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

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

Jenkinsfile Runner generates exception when invoking the app from another directory. It does not lead to the execution failure, but it prints NPE to the log. It would be great if Jenkinsfile Runner Filesystem SCM was using the current dir everywhere as documented

onenashev@LAPTOP-25K65LOS:/c/Users/Oleg/Documents/jenkins/jfr/jenkinsfile-runner/demo/declarative-pipeline$ ../../app/target/app

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

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_

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