From 69a6dc03dee6fcfb17bc4f855fd1913114aff89e Mon Sep 17 00:00:00 2001 From: "update-envoy[bot]" <135279899+update-envoy[bot]@users.noreply.github.com> Date: Thu, 7 Sep 2023 15:08:59 +0000 Subject: [PATCH] http: new runtime flag to disable name downgrading in per filter config searching (#29407) * http: new runtime flag to disable name downgrading in per filter config searching Signed-off-by: wbpcode * fix spelling error Signed-off-by: wbpcode * update docs/comments Signed-off-by: wbpcode * minor update Signed-off-by: wbpcode * address comments Signed-off-by: wbpcode --------- Signed-off-by: wbpcode Mirrored from https://github.com/envoyproxy/envoy @ 1b41133d41c0ae1ba8782d41414162f381083094 --- envoy/config/route/v3/route.proto | 12 +++---- envoy/config/route/v3/route_components.proto | 37 +++++++------------- 2 files changed, 16 insertions(+), 33 deletions(-) diff --git a/envoy/config/route/v3/route.proto b/envoy/config/route/v3/route.proto index d7bc8541..237bddeb 100644 --- a/envoy/config/route/v3/route.proto +++ b/envoy/config/route/v3/route.proto @@ -142,15 +142,11 @@ message RouteConfiguration { // For users who want to only match path on the "" portion, this option should be true. bool ignore_path_parameters_in_path_matching = 15; - // The typed_per_filter_config field can be used to provide RouteConfiguration level per filter config. - // The key should match the :ref:`filter config name + // This field can be used to provide RouteConfiguration level per filter config. The key should match the + // :ref:`filter config name // `. - // The canonical filter name (e.g., ``envoy.filters.http.buffer`` for the HTTP buffer filter) can also - // be used for the backwards compatibility. If there is no entry referred by the filter config name, the - // entry referred by the canonical filter name will be provided to the filters as fallback. - // - // Use of this field is filter specific; - // see the :ref:`HTTP filter documentation ` for if and how it is utilized. + // See :ref:`Http filter route specific config ` + // for details. // [#comment: An entry's value may be wrapped in a // :ref:`FilterConfig` // message to specify additional options.] diff --git a/envoy/config/route/v3/route_components.proto b/envoy/config/route/v3/route_components.proto index 014bb0d9..1800ee91 100644 --- a/envoy/config/route/v3/route_components.proto +++ b/envoy/config/route/v3/route_components.proto @@ -153,15 +153,11 @@ message VirtualHost { // to configure the CORS HTTP filter. CorsPolicy cors = 8 [deprecated = true, (envoy.annotations.deprecated_at_minor_version) = "3.0"]; - // The per_filter_config field can be used to provide virtual host-specific configurations for filters. - // The key should match the :ref:`filter config name + // This field can be used to provide virtual host level per filter config. The key should match the + // :ref:`filter config name // `. - // The canonical filter name (e.g., ``envoy.filters.http.buffer`` for the HTTP buffer filter) can also - // be used for the backwards compatibility. If there is no entry referred by the filter config name, the - // entry referred by the canonical filter name will be provided to the filters as fallback. - // - // Use of this field is filter specific; - // see the :ref:`HTTP filter documentation ` for if and how it is utilized. + // See :ref:`Http filter route specific config ` + // for details. // [#comment: An entry's value may be wrapped in a // :ref:`FilterConfig` // message to specify additional options.] @@ -292,15 +288,11 @@ message Route { // Decorator for the matched route. Decorator decorator = 5; - // The per_filter_config field can be used to provide route-specific configurations for filters. - // The key should match the :ref:`filter config name + // This field can be used to provide route specific per filter config. The key should match the + // :ref:`filter config name // `. - // The canonical filter name (e.g., ``envoy.filters.http.buffer`` for the HTTP buffer filter) can also - // be used for the backwards compatibility. If there is no entry referred by the filter config name, the - // entry referred by the canonical filter name will be provided to the filters as fallback. - // - // Use of this field is filter specific; - // see the :ref:`HTTP filter documentation ` for if and how it is utilized. + // See :ref:`Http filter route specific config ` + // for details. // [#comment: An entry's value may be wrapped in a // :ref:`FilterConfig` // message to specify additional options.] @@ -451,16 +443,11 @@ message WeightedCluster { items {string {well_known_regex: HTTP_HEADER_NAME strict: false}} }]; - // The per_filter_config field can be used to provide weighted cluster-specific configurations - // for filters. - // The key should match the :ref:`filter config name + // This field can be used to provide weighted cluster specific per filter config. The key should match the + // :ref:`filter config name // `. - // The canonical filter name (e.g., ``envoy.filters.http.buffer`` for the HTTP buffer filter) can also - // be used for the backwards compatibility. If there is no entry referred by the filter config name, the - // entry referred by the canonical filter name will be provided to the filters as fallback. - // - // Use of this field is filter specific; - // see the :ref:`HTTP filter documentation ` for if and how it is utilized. + // See :ref:`Http filter route specific config ` + // for details. // [#comment: An entry's value may be wrapped in a // :ref:`FilterConfig` // message to specify additional options.]