config: support dynamic_forward_proxy #433
Comments
rebello95
added a commit
that referenced
this issue
Sep 12, 2019
Adds support for setting the domain used in the base cluster of the Envoy config. This is necessary until `dynamic_forward_proxy` is working (see #433). Signed-off-by: Michael Rebello <me@michaelrebello.com>
rebello95
added a commit
that referenced
this issue
Sep 12, 2019
Adds support for setting the domain used in the base cluster of the Envoy config. This is necessary until `dynamic_forward_proxy` is working (see #433). Android change will come in a follow-up PR. Risk Level: Low Testing: Locally on demos & unit tests Signed-off-by: Michael Rebello <me@michaelrebello.com>
|
fixed by #616 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have a
dynamic_forward_proxyconfiguration in the base config file that's checked in to the repo, but it doesn't function when using the direct API (and thebasecluster must be used with a hardcoded domain for now).We'll need to support the
dynamic_forward_proxyconfiguration so consumers don't need to pre-define acceptable domains for routing when creating Envoy instances.The text was updated successfully, but these errors were encountered: