mirror of https://github.com/hashicorp/consul
8728a4496c
* Add Tproxy support to Envoy Extensions (this is needed for service to service validation) * Add validation for Envoy configuration for an upstream service * Use both /config_dump and /cluster to validate Envoy configuration This is because of a bug in Envoy where the EndpointsConfigDump does not include a cluster_name, making it impossible to match an endpoint to verify it exists. This removes endpoints support for builtin extensions since only the validate plugin was using it, and it is no longer used. It also removes test cases for endpoint validation. Endpoints validation now only occurs in the top level test from config_dump and clusters json files. Co-authored-by: Eric <eric@haberkorn.co> |
||
|---|---|---|
| .. | ||
| lambda-connect-proxy-opposite-meta.latest.golden | ||
| lambda-connect-proxy-tproxy.latest.golden | ||
| lambda-connect-proxy-with-terminating-gateway-upstream.latest.golden | ||
| lambda-connect-proxy.latest.golden | ||
| lambda-terminating-gateway-with-service-resolvers.latest.golden | ||
| lambda-terminating-gateway.latest.golden | ||
| lua-connect-proxy-with-terminating-gateway-upstream.latest.golden | ||
| lua-inbound-applies-to-inbound.latest.golden | ||
| lua-inbound-doesnt-applies-to-upstreams.latest.golden | ||
| lua-outbound-applies-to-upstreams.latest.golden | ||
| lua-outbound-doesnt-apply-to-inbound.latest.golden | ||