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

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

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!

Checklist

• Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a questi

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):

Describe the bug
When running npx serverless --debug if the next build process fails with an error it is not displayed in the output and the deployment hangs forever.

To Reproduce
Steps to reproduce the behavior:

1. Create a reproducible error in pages/index.js (in my case an import statement was incorrect)
2. Run npx serverless --debug
3. Output displays "appName Deplo