faas

Is your feature request related to a problem? Please describe.
Currently, there are two ways to create HTTPTrigger using the fission command.

1. fission fn create with below parameters

  --url=''                              URL pattern (See gorilla/mux supported patterns)
  --prefix=''                           Prefix with which functions are exposed. NOTE: Prefix takes
    

Environment details:

• local deployment (standalone openwhisk)

Steps to reproduce the issue:

1. create a web action using this function:

> cat t.js
const main = () => ({
  "body": {
    "message": "hello"
  },
  "statusCode": 442
})

2. invoke the web action

> wsk action update t t.js --web true
> curl -X POST `wsk action get t --url`
{
  "code": "b86c3c

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

If we override PHP_INI_SCAN_DIR then the "special php.ini" files will not be used.
Ie: https://github.com/brefphp/bref/blob/0.5.9/runtime/layers/fpm/php.ini

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

The ingress template https://github.com/openfaas/faas-netes/blob/master/chart/openfaas/templates/ingress.yaml uses
deprecated extensions/v1beta1 version. Due to the https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/, the API version should be migrated to networking.k8s.io/v1beta1

What needs to be done

Update terraform scripts to latest version and retest that they work as expected.

Context

We're trailing behind several versions, and once we get to v1.0 - apparently, there are fewer backwards compatibility issues expected between minor releases of terraform.

https://github.com/openfaas/

https://github.com/metrue/fx/runs/2779702719?check_suite_focus=true

jenkinsci/jenkinsfile-runner#511 by @pawoolley introduced support for a new lint command support for Jenkinsfile Runner. IMHO it is a new useful use-case for Jenkinsfile Runner users, and it deserves a documentation section in https://github.com/jenkinsci/jenkinsfile-runner/tree/master/docs/using

Acceptance criteria:

• A new "linting" or "pipeline verification" pag

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

Expected Behaviour

The following should generate a Rancher Rio Service definition:

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

apiVersion: rio.cat