api-gateway

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.

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul

Issue description

Some plugins support vars matching, such as traffic-split.

"plugins": {
        "traffic-split": {
            "rules": [
                {
                    "match": [
                        {
                            "vars": [
                                ["arg_name","==","test"]
                            ]
                        }
          

Feature Request

Is your feature request related to a problem? Please describe

Is it nessary to support RocketMQ

• Two ways to user it.
  • As a way to data sync from admin to bootstrap.
  • As a plugin to send mq message by request from bootstrap.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Describe the requested changes
Github issue links in Changelog docs are broken. There is an extra parenthesis at the end of each link that causes link traversal to fail.

Link to any relevant existing docs

1. https://docs.solo.io/gloo-edge/latest/reference/changelog/open_source/
   Note that the closing parenthesis at the end of each github link is blue (i.e., part of the link itself).

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

Is your feature request related to a problem? Please describe.
Yarn packages aren't being cached on e2e tests and build workflows

Describe the solution you'd like
Add caching for npm packages and Cypress (except @sls-next packages) so that workflows will be faster to run

Describe alternatives you've considered
N/A, it will help improve CI workflow speed

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.