From 04b8c0788b498a740072e9a155bf24e710182e81 Mon Sep 17 00:00:00 2001 From: Jose Ulises Nino Rivera Date: Tue, 30 Jan 2018 11:29:54 -0800 Subject: [PATCH] tcp proxy: add warning for deprecated_v1 field (#442) Signed-off-by: Jose Nino --- envoy/api/v2/filter/network/tcp_proxy.proto | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/envoy/api/v2/filter/network/tcp_proxy.proto b/envoy/api/v2/filter/network/tcp_proxy.proto index 8febffaa..4881f448 100644 --- a/envoy/api/v2/filter/network/tcp_proxy.proto +++ b/envoy/api/v2/filter/network/tcp_proxy.proto @@ -109,7 +109,16 @@ message TcpProxy { // TCP Proxy filter configuration using deprecated V1 format. This is required for complex // routing until filter chain matching in the listener is implemented. - DeprecatedV1 deprecated_v1 = 6; + // + // .. attention:: + // + // Using this field will lead to `problems loading the configuration + // `_. If you + // want to configure the filter using v1 config structure, please make this + // field a boolean with value ``true`` and configure via the opaque ``value`` field + // like is suggested in the filter `README + // `_. + DeprecatedV1 deprecated_v1 = 6 [deprecated = true]; // The maximum number of unsuccessful connection attempts that will be made before // giving up. If the parameter is not specified, 1 connection attempt will be made.