gRPC

🐛 Bug Report

protoc-gen-openapiv2 offers to mark properties as required based on the google.api.field_behavior field option, but it adds the "required": ["<property>"], annotation to the property itself in addition to adding it to the object containing the property.

https://grpc-ecosystem.github.io/grpc-gateway/docs/mapping/customizing_openapi_output/#using-googleapifield_behavior

Allow to close tabs by hovering over a tab and clicking the middle mouse button.
Just like in web browsers. :)

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

Before you submit this issue, you has been search all existed issues and search the documentation

• [] I've been search all existed issues
• [] I've been read all documentation

Describe your question

How should I use alicloud MNS?

AnnotatedServiceBindingBuilder and VirtualHostAnnotatedServiceBindingBuilder currently don't share a common interface for its methods, such as pathPrefix() and exceptionHandlers(). This means, a contributor can add a builder method to one builder but not to the other by mistake. By making both builder extend a new interface AnnotatedServiceConfigSetters, we could prevent such a mistake.

Version

No response

Is your feature request related to a problem? Please describe.

GIven an AuthConfig CR with multiple config blocks
When the end-user is authenticated / when the userId is created
Put it into filter metadata so that the next item in the auth chain can read the value

Example:
With the following AC

apiVersion: enterprise.gloo.solo.io/v1
kind: AuthConf