gRPC

背景和动机

我们不希望将一些敏感的内容提交到 git 仓库中，所以这些敏感内容我们会和提交到 git 仓库的配置文件分离。

我们将这些机密内容放在 dotenv运行时加载到环境变量 或是 直接存于环境变量 中。

除此之外，配置可能因为程序运行环境发生改变，而需要动态的进行配置。

所以我们希望 kratos 能够在配置文件中动态的识别环境变量占位符，并使用环境变量值替换配置的内容。

提议的方案

修订1：提议方案需根据 @tonybase 描述建议修正
修订2：语义占位符采用 os.Expand 解析规则完成，废弃修订1的讨论

提案在配置文件中，通过占位符来替换环境变量

🐛 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

We could add MediaType.BROTLI and MediaType.ZSTD which are the compression format gaining popularity these days.

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).

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