apis

There are many inactive PRs that have already been revised and with their APIs according to our addition criteria. These PRs are just waiting for some correction that was requested by one of the maintainers, and as they are inactive PRs, they will likely not be done.

Inactive PRs must be closed and their APIs added if they still meet our criteria.

Maintainers can add the APIs of these PRs in

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.

Summary

It's annoying to remember the right protobuf structure for envoy socket address. There is a helper in pkg/envoy/accesslog/v3/helper_test.go that wraps the boilerplate.

We should move this to a regular util package and use it everywhere.

Describe the event source. What app is this for, and what event does the trigger correspond to?
Slack's API exposes access activity like logins. It's useful sometimes to trigger off of someone's first login to run some welcome actions or log the activity in a database elsewhere. It will probably require some polling, but we could hit the team.accessLogs endpoint periodically to see if anyon

A Kong SNI can only point to a single certificate. Per Kong/kubernetes-ingress-controller#1268 (comment), misconfigured Kubernetes resources can attempt to point an SNI to multiple certificates.

While we do avoid adding attached SNIs to new certificates, we do

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

These keys can be used in various combinations ( eg. { "environment": "prod", released: true, consumer: "Foo" } ). Please allow any combination

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir