Piotr Sikora

This is on the roadmap (see: https://github.com/envoyproxy/envoy/issues/22557, https://github.com/proxy-wasm/proxy-wasm-cpp-host/issues/127), but it's not implemented yet. As for the workaround for accessing Envoy's configuration, you might want to use HTTP callouts to access...

Did you look at [examples/http_config](https://github.com/proxy-wasm/proxy-wasm-rust-sdk/tree/v0.2.1/examples/http_config)? Does it address your use case?

Did you consider using ECDS to update only Proxy-Wasm plugin's configuration and not "complete" envoy.yaml, or is that also not possible due to security rules? In any case, the read-only...

gRPC's initial metadata is supplemental metadata that's encoded as HTTP headers, but those shouldn't be used as HTTP headers, and you cannot use it to override HTTP headers. Having said...

Also, answering your original question, I think you should be able to configure `:authority` in `upstream-cluster's` configuration in Envoy using [the Endpoint's `hostname` field](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/endpoint/v3/endpoint_components.proto#config-endpoint-v3-endpoint).

> That has caused a lot of confusion to anyone interested in this project, not only the end users but also those who is willing to contirbute. While I agree...

> “Believe” may have been the wrong word, because the situation is awkward. It is well known there is a problem with this specification, and I took action to remove...

> > I think the timeframe for the ABI documentation was also roughly 2 weeks (from now). > > @mpwarres sorry I could not get this point on timeline. IIUC,...

> I think proxy-wasm ecosystem and ultimately the community around is bigger than any individual. Something that several projects depend on cannot depend on a single person which isolated work...

Still working on it. I should have it out tomorrow evening, or over the weekend at the latest.