gRPC

After PR #1401 merged, many of our sub modules are failing lint, we should fix all of them.

To fix these, take a look at hack/.lintcheck_failures for a list of currently lint failed modules.

You can check a module by removing it from the .lintcheck_failures list and running make fix to auto fix some lint errors.

🐛 Bug Report

To Reproduce

package api.svc;

option go_package = "api/svc";

  rpc GetTrieNode(api.infra.GetTrieNodeReq) returns (api.infra.KVNode) {
    option (google.api.http) = {
      post: "/trie/node:get"
      body: "*"
      additional_bindings {
        get: "/trie/node/{id}"
      }
      additional_bindings {
        get: "/trie/node/path/{path}"
      }

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

When using type google.protobuf.Timestamp, BloomRPC maps this to an object, e.g.:

"create_time": {
  "seconds": "1562723637",
  "nanos": 928852400
}

However, the Google API Design Guide specifies that the string representation should be RFC 3339 format, e.g. "2014-07-30T10:43:17Z"

This JSON mapp

我需要

可我在hyperf中不知道该如何使用write

If a user performs a blocking task in decorator chains or services, they have to 1) submit a task to a blocking task executor,
2) pass the result to a CompletableFuture and 3) wrap the CompletableFuture with HttpResponse.from().

sb.serviceUnder("/web", service.decorate((delegate, ctx, req) -> {
    CompletableFuture<HttpResponse> future = new CompletableFuture<>();
    ctx.bl

As we all know golang has give us the feature that convert proto to json with https://github.com/golang/protobuf/blob/master/jsonpb/encode.go ,and with encode.go ,we can define diffrent style like casesensitive , emit empty , json indent and so on , we can see [Customizing Protobuf JSON Serialization in Go](https://seb-nyberg.medi

Is your feature request related to a problem? Please describe.
Currently, there's no way in Gloo Edge to perform similar than what the regex_rewrite option provide.

Describe the solution you'd like
Expose the regex_rewrite (https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-redirectaction) option in Gloo Edge