envoy-types: update generated files

Author: flemosr

envoy-types/src/generated/envoy.admin.v3.rs

@@ -262,8 +262,8 @@ pub struct HostStatus {
     ///
     /// .. note::
     ///
-    /// The message will be missing if the host didn’t receive enough traffic to compute a success rate, or if the
-    /// cluster didn’t have enough hosts to perform outlier ejection based on success rate.
+    /// The message will be missing if the host didn't receive enough traffic to compute a success rate, or if the
+    /// cluster didn't have enough hosts to perform outlier ejection based on success rate.
     #[prost(message, optional, tag = "8")]
     pub local_origin_success_rate: ::core::option::Option<
         super::super::r#type::v3::Percent,
@@ -289,18 +289,22 @@ pub struct HostHealthStatus {
     /// health checking.
     #[prost(bool, tag = "5")]
     pub pending_dynamic_removal: bool,
-    /// The host has not yet been health checked.
+    /// The host is awaiting first health check.
     #[prost(bool, tag = "6")]
     pub pending_active_hc: bool,
     /// The host should be excluded from panic, spillover, etc. calculations because it was explicitly
     /// taken out of rotation via protocol signal and is not meant to be routed to.
     #[prost(bool, tag = "7")]
     pub excluded_via_immediate_hc_fail: bool,
-    /// The host failed active HC due to timeout.
+    /// The host failed active health check due to timeout.
     #[prost(bool, tag = "8")]
     pub active_hc_timeout: bool,
-    /// Health status as reported by EDS. Note: only HEALTHY and UNHEALTHY are currently supported
-    /// here.
+    /// Health status as reported by EDS.
+    ///
+    /// .. note::
+    ///
+    /// Currently, only `HEALTHY` and `UNHEALTHY` are supported.
+    ///
     /// \[\#comment:TODO(mrice32): pipe through remaining EDS health status possibilities.\]
     #[prost(enumeration = "super::super::config::core::v3::HealthStatus", tag = "3")]
     pub eds_health_status: i32,

envoy-types/src/generated/envoy.config.bootstrap.v3.rs

@@ -305,9 +305,7 @@ pub mod bootstrap {
         >,
         /// If a network based configuration source is specified for :ref:`cds_config  <envoy_v3_api_field_config.bootstrap.v3.Bootstrap.DynamicResources.cds_config>`, it's necessary
         /// to have some initial cluster definitions available to allow Envoy to know
-        /// how to speak to the management server. These cluster definitions may not
-        /// use :ref:`EDS <arch_overview_dynamic_config_eds>` (i.e. they should be static
-        /// IP or DNS-based).
+        /// how to speak to the management server.
         #[prost(message, repeated, tag = "2")]
         pub clusters: ::prost::alloc::vec::Vec<
             super::super::super::cluster::v3::Cluster,

envoy-types/src/generated/envoy.config.cluster.v3.rs

@@ -429,11 +429,13 @@ pub struct Cluster {
     pub name: ::prost::alloc::string::String,
     ///
     /// An optional alternative to the cluster name to be used for observability. This name is used
-    /// emitting stats for the cluster and access logging the cluster name. This will appear as
+    /// for emitting stats for the cluster and access logging the cluster name. This will appear as
     /// additional information in configuration dumps of a cluster's current status as
     /// : ref:`observability_name <envoy_v3_api_field_admin.v3.ClusterStatus.observability_name>`
-    ///   and as an additional tag "upstream_cluster.name" while tracing. Note: Any `:` in the name
-    ///   will be converted to `_` when emitting statistics. This should not be confused with
+    ///   and as an additional tag "upstream_cluster.name" while tracing.
+    ///
+    /// .. note::
+    /// Any `:` in the name will be converted to `_` when emitting statistics. This should not be confused with
     /// : ref:`Router Filter Header <config_http_filters_router_x-envoy-upstream-alt-stat-name>`.
     #[prost(string, tag = "28")]
     pub alt_stat_name: ::prost::alloc::string::String,
@@ -1489,7 +1491,8 @@ pub mod cluster {
         /// If this is not set, we default to a merge window of 1000ms. To disable it, set the merge
         /// window to 0.
         ///
-        /// Note: merging does not apply to cluster membership changes (e.g.: adds/removes); this is
+        /// .. note::
+        /// Merging does not apply to cluster membership changes (e.g.: adds/removes); this is
         /// because merging those updates isn't currently safe. See
         /// <https://github.com/envoyproxy/envoy/pull/3941.>
         #[prost(message, optional, tag = "4")]

envoy-types/src/generated/envoy.config.common.matcher.v3.rs

@@ -9,8 +9,8 @@
 /// Please use the syntactically equivalent :ref:`matching API <envoy_v3_api_msg_.xds.type.matcher.v3.Matcher>`
 #[derive(Clone, PartialEq, ::prost::Message)]
 pub struct Matcher {
-    /// Optional OnMatch to use if the matcher failed.
-    /// If specified, the OnMatch is used, and the matcher is considered
+    /// Optional `OnMatch` to use if the matcher failed.
+    /// If specified, the `OnMatch` is used, and the matcher is considered
     /// to have matched.
     /// If not specified, the matcher is considered not to have matched.
     #[prost(message, optional, boxed, tag = "3")]
@@ -25,6 +25,17 @@ pub mod matcher {
     /// What to do if a match is successful.
     #[derive(Clone, PartialEq, ::prost::Message)]
     pub struct OnMatch {
+        /// If true, the action will be taken but the caller will behave as if no
+        /// match was found. This applies both to actions directly encoded in the
+        /// action field and to actions returned from a nested matcher tree in the
+        /// matcher field. A subsequent matcher on_no_match action will be used
+        /// instead.
+        ///
+        /// This field is not supported in all contexts in which the matcher API is
+        /// used. If this field is set in a context in which it's not supported,
+        /// the resource will be rejected.
+        #[prost(bool, tag = "3")]
+        pub keep_matching: bool,
         #[prost(oneof = "on_match::OnMatch", tags = "1, 2")]
         pub on_match: ::core::option::Option<on_match::OnMatch>,
     }
@@ -109,7 +120,7 @@ pub mod matcher {
                 /// A list of predicates to be AND-ed together.
                 #[prost(message, tag = "3")]
                 AndMatcher(PredicateList),
-                /// The invert of a predicate
+                /// The inverse of a predicate
                 #[prost(message, tag = "4")]
                 NotMatcher(::prost::alloc::boxed::Box<super::Predicate>),
             }
@@ -243,9 +254,9 @@ pub struct HttpHeadersMatch {
 ///
 /// .. attention::
 ///
-/// Searching for patterns in HTTP body is potentially cpu intensive. For each specified pattern, http body is scanned byte by byte to find a match.
+/// Searching for patterns in HTTP body is potentially CPU-intensive. For each specified pattern, HTTP body is scanned byte by byte to find a match.
 /// If multiple patterns are specified, the process is repeated for each pattern. If location of a pattern is known, `bytes_limit` should be specified
-/// to scan only part of the http body.
+/// to scan only part of the HTTP body.
 #[derive(Clone, PartialEq, ::prost::Message)]
 pub struct HttpGenericBodyMatch {
     /// Limits search to specified number of bytes - default zero (no limit - match entire captured buffer).

envoy-types/src/generated/envoy.config.core.v3.rs

@@ -215,9 +215,14 @@ pub struct SocketAddress {
     /// IPv6 space as `::FFFF:<IPv4-address>`.
     #[prost(bool, tag = "6")]
     pub ipv4_compat: bool,
-    /// The Linux network namespace to bind the socket to. If this is set, Envoy will
-    /// create the socket in the specified network namespace. Only supported on Linux.
-    /// \[\#not-implemented-hide:\]
+    /// Filepath that specifies the Linux network namespace this socket will be created in (see `man 7  network_namespaces`). If this field is set, Envoy will create the socket in the specified
+    /// network namespace.
+    ///
+    /// .. note::
+    /// Setting this parameter requires Envoy to run with the `CAP_NET_ADMIN` capability.
+    ///
+    /// .. attention::
+    /// Network namespaces are only configurable on Linux. Otherwise, this field has no effect.
     #[prost(string, tag = "7")]
     pub network_namespace_filepath: ::prost::alloc::string::String,
     #[prost(oneof = "socket_address::PortSpecifier", tags = "3, 4")]
@@ -1976,7 +1981,8 @@ pub mod health_check {
         /// `/healthcheck`.
         #[prost(string, tag = "2")]
         pub path: ::prost::alloc::string::String,
-        /// \[\#not-implemented-hide:\] HTTP specific payload.
+        /// HTTP specific payload to be sent as the request body during health checking.
+        /// If specified, the method should support a request body (POST, PUT, PATCH, etc.).
         #[prost(message, optional, tag = "3")]
         pub send: ::core::option::Option<Payload>,
         /// Specifies a list of HTTP expected responses to match in the first `response_buffer_size` bytes of the response body.
@@ -2043,7 +2049,8 @@ pub mod health_check {
             super::super::super::super::r#type::matcher::v3::StringMatcher,
         >,
         /// HTTP Method that will be used for health checking, default is "GET".
-        /// GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, PATCH methods are supported, but making request body is not supported.
+        /// GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, PATCH methods are supported.
+        /// Request body payloads are supported for POST, PUT, PATCH, and OPTIONS methods only.
         /// CONNECT method is disallowed because it is not appropriate for health check request.
         /// If a non-200 response is expected by the method, it needs to be set in :ref:`expected_statuses <envoy_v3_api_field_config.core.v3.HealthCheck.HttpHealthCheck.expected_statuses>`.
         #[prost(enumeration = "super::RequestMethod", tag = "13")]
@@ -2568,8 +2575,11 @@ pub struct QuicProtocolOptions {
     /// `Initial stream-level flow-control receive window  <<https://tools.ietf.org/html/draft-ietf-quic-transport-34#section-4.1>`\_> size. Valid values range from
     /// 1 to 16777216 (2^24, maximum supported by QUICHE) and defaults to 16777216 (16 * 1024 * 1024).
     ///
-    /// NOTE: 16384 (2^14) is the minimum window size supported in Google QUIC. If configured smaller than it, we will use 16384 instead.
-    /// QUICHE IETF Quic implementation supports 1 bytes window. We only support increasing the default window size now, so it's also the minimum.
+    /// .. note::
+    ///
+    /// 16384 (2^14) is the minimum window size supported in Google QUIC. If configured smaller than it, we will use
+    /// 16384 instead. QUICHE IETF Quic implementation supports 1 bytes window. We only support increasing the default
+    /// window size now, so it's also the minimum.
     ///
     /// This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
     /// QUIC stream send and receive buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
@@ -2579,10 +2589,12 @@ pub struct QuicProtocolOptions {
         super::super::super::super::google::protobuf::UInt32Value,
     >,
     /// Similar to `initial_stream_window_size`, but for connection-level
-    /// flow-control. Valid values rage from 1 to 25165824 (24MB, maximum supported by QUICHE) and defaults
+    /// flow-control. Valid values range from 1 to 25165824 (24MB, maximum supported by QUICHE) and defaults
     /// to 25165824 (24 * 1024 * 1024).
     ///
-    /// NOTE: 16384 (2^14) is the minimum window size supported in Google QUIC. We only support increasing the default
+    /// .. note::
+    ///
+    /// 16384 (2^14) is the minimum window size supported in Google QUIC. We only support increasing the default
     /// window size now, so it's also the minimum.
     #[prost(message, optional, tag = "3")]
     pub initial_connection_window_size: ::core::option::Option<
@@ -2768,7 +2780,7 @@ pub struct HttpProtocolOptions {
     /// The default value for responses can be overridden by setting runtime key `envoy.reloadable_features.max_response_headers_count`.
     /// Downstream requests that exceed this limit will receive a 431 response for HTTP/1.x and cause a stream
     /// reset for HTTP/2.
-    /// Upstream responses that exceed this limit will result in a 503 response.
+    /// Upstream responses that exceed this limit will result in a 502 response.
     #[prost(message, optional, tag = "2")]
     pub max_headers_count: ::core::option::Option<
         super::super::super::super::google::protobuf::UInt32Value,
@@ -2783,9 +2795,12 @@ pub struct HttpProtocolOptions {
     /// : ref:`HTTP Connection Manager  <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.common_http_protocol_options>`.
     ///
     ///
-    /// Note: currently some protocol codecs impose limits on the maximum size of a single header:
-    /// HTTP/2 (when using nghttp2) limits a single header to around 100kb.
-    /// HTTP/3 limits a single header to around 1024kb.
+    /// .. note::
+    ///
+    /// Currently some protocol codecs impose limits on the maximum size of a single header.
+    ///
+    /// * HTTP/2 (when using nghttp2) limits a single header to around 100kb.
+    /// * HTTP/3 limits a single header to around 1024kb.
     #[prost(message, optional, tag = "7")]
     pub max_response_headers_kb: ::core::option::Option<
         super::super::super::super::google::protobuf::UInt32Value,
@@ -2798,9 +2813,15 @@ pub struct HttpProtocolOptions {
     >,
     /// Action to take when a client request with a header name containing underscore characters is received.
     /// If this setting is not specified, the value defaults to ALLOW.
-    /// Note: upstream responses are not affected by this setting.
-    /// Note: this only affects client headers. It does not affect headers added
-    /// by Envoy filters and does not have any impact if added to cluster config.
+    ///
+    /// .. note::
+    ///
+    /// Upstream responses are not affected by this setting.
+    ///
+    /// .. note::
+    ///
+    /// This only affects client headers. It does not affect headers added by Envoy filters and does not have any
+    /// impact if added to cluster config.
     #[prost(
         enumeration = "http_protocol_options::HeadersWithUnderscoresAction",
         tag = "5"
@@ -2944,6 +2965,7 @@ pub struct Http1ProtocolOptions {
     /// If unset, HTTP/1 parser is selected based on
     /// envoy.reloadable_features.http1_use_balsa_parser.
     /// See issue #21245.
+    #[deprecated]
     #[prost(message, optional, tag = "9")]
     pub use_balsa_parser: ::core::option::Option<
         super::super::super::super::google::protobuf::BoolValue,
@@ -3065,8 +3087,10 @@ pub struct Http2ProtocolOptions {
     /// (2^16 - 1, HTTP/2 default) to 2147483647 (2^31 - 1, HTTP/2 maximum) and defaults to 268435456
     /// (256 * 1024 * 1024).
     ///
-    /// NOTE: 65535 is the initial window size from HTTP/2 spec. We only support increasing the default
-    /// window size now, so it's also the minimum.
+    /// .. note::
+    ///
+    /// 65535 is the initial window size from HTTP/2 spec. We only support increasing the default window size now,
+    /// so it's also the minimum.
     ///
     /// This field also acts as a soft limit on the number of bytes Envoy will buffer per-stream in the
     /// HTTP/2 codec buffers. Once the buffer reaches this pointer, watermark callbacks will fire to
@@ -3247,7 +3271,7 @@ pub struct GrpcProtocolOptions {
     pub http2_protocol_options: ::core::option::Option<Http2ProtocolOptions>,
 }
 /// A message which allows using HTTP/3.
-/// \[\#next-free-field: 8\]
+/// \[\#next-free-field: 9\]
 #[derive(Clone, PartialEq, ::prost::Message)]
 pub struct Http3ProtocolOptions {
     #[prost(message, optional, tag = "1")]
@@ -3283,6 +3307,10 @@ pub struct Http3ProtocolOptions {
     /// This can be useful for trading off CPU vs bandwidth when an upstream HTTP/3 connection multiplexes multiple downstream connections.
     #[prost(bool, tag = "7")]
     pub disable_qpack: bool,
+    /// Disables connection level flow control for HTTP/3 streams. This is useful in situations where the streams share the same connection
+    /// but originate from different end-clients, so that each stream can make progress independently at non-front-line proxies.
+    #[prost(bool, tag = "8")]
+    pub disable_connection_flow_control_for_streams: bool,
 }
 /// A message to control transformations to the :scheme header
 #[derive(Clone, PartialEq, ::prost::Message)]

envoy-types/src/generated/envoy.config.endpoint.v3.rs

@@ -324,7 +324,8 @@ pub mod cluster_load_assignment {
         /// this calculation.
         ///
         ///
-        /// Note: this is not currently implemented for
+        /// .. note::
+        /// This is not currently implemented for
         /// : ref:`locality weighted load balancing <arch_overview_load_balancing_locality_weighted_lb>`.
         #[prost(bool, tag = "6")]
         pub weighted_priority_health: bool,

envoy-types/src/generated/envoy.config.grpc_credential.v3.rs

@@ -1,23 +1,5 @@
 // This file is @generated by prost-build.
 #[derive(Clone, PartialEq, ::prost::Message)]
-pub struct AwsIamConfig {
-    /// The `service namespace  <<https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#genref-aws-service-namespaces>`\_>
-    /// of the Grpc endpoint.
-    ///
-    /// Example: appmesh
-    #[deprecated]
-    #[prost(string, tag = "1")]
-    pub service_name: ::prost::alloc::string::String,
-    /// The `region <<https://docs.aws.amazon.com/general/latest/gr/rande.html>`\_> hosting the Grpc
-    /// endpoint. If unspecified, the extension will use the value in the `AWS_REGION` environment
-    /// variable.
-    ///
-    /// Example: us-west-2
-    #[deprecated]
-    #[prost(string, tag = "2")]
-    pub region: ::prost::alloc::string::String,
-}
-#[derive(Clone, PartialEq, ::prost::Message)]
 pub struct FileBasedMetadataConfig {
     /// Location or inline data of secret to use for authentication of the Google gRPC connection
     /// this secret will be attached to a header of the gRPC connection