Serverless

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

Update daprd to compile with Go 1.17.

Release notes: https://golang.org/doc/go1.17.

Describe the bug

Serverless: Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "provider.environment.CUBEJS_APP": Value not found at "self" source,
              - Cannot resolve variable at "functions.cubejsProcess.events.0.event.resource": Value not found at "self" source
            From a next major this will be

🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana

Description

Add CLI bash completion of APIs and environments. Environments is lower priority.

Additional Context

• The operator will need an endpoint to provide the list of APIs. Which env to use? Pull it from the still-being-typed command (e.g. if --env aws is typed already)?
• Env names can be read from the CLI config
• [Cobra docs](https://github.com/spf13/cobra/blob/master

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
    

Issue description

The default_conn_delay of the limit-conn plug-in is used to control the delay of forwarding to upstreams when the connection exceeds a certain threshold, but after actual testing, it is found that this delay time is not strictly in accordance with the configured delay time.

https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.lua#L98-L101

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