config: extending usage of EnvoyMobileHttpConnectionManager (#17407)

#17110 the EnvoyMobileHttpConnectionManager but it turns out it's instantiated either as a standard network filter (needs a name) or as an API listener (which only accepted HttpConnectionManager)

Fixing both issues.

Risk Level: low
Testing: unit tests
Docs Changes: n/a
Release Notes: n/a
Part of envoyproxy/envoy-mobile#1540

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Mirrored from https://github.com/envoyproxy/envoy @ 463eda2f3895fbb24c1fcd085a15d00d12a94079
pull/624/head
data-plane-api(Azure Pipelines) 4 years ago
parent ca81738dc4
commit b73e171a20
  1. 1
      envoy/config/listener/v3/api_listener.proto
  2. 1
      envoy/config/listener/v4alpha/api_listener.proto
  3. 1
      envoy/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto
  4. 1
      envoy/extensions/filters/network/http_connection_manager/v4alpha/http_connection_manager.proto

@ -23,6 +23,7 @@ message ApiListener {
// The type in this field determines the type of API listener. At present, the following
// types are supported:
// envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager (HTTP)
// envoy.extensions.filters.network.http_connection_manager.v3.EnvoyMobileHttpConnectionManager (HTTP)
// [#next-major-version: In the v3 API, replace this Any field with a oneof containing the
// specific config message for each type of API listener. We could not do this in v2 because
// it would have caused circular dependencies for go protos: lds.proto depends on this file,

@ -23,6 +23,7 @@ message ApiListener {
// The type in this field determines the type of API listener. At present, the following
// types are supported:
// envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager (HTTP)
// envoy.extensions.filters.network.http_connection_manager.v3.EnvoyMobileHttpConnectionManager (HTTP)
// [#next-major-version: In the v3 API, replace this Any field with a oneof containing the
// specific config message for each type of API listener. We could not do this in v2 because
// it would have caused circular dependencies for go protos: lds.proto depends on this file,

@ -1008,6 +1008,7 @@ message RequestIDExtension {
// [#protodoc-title: Envoy Mobile HTTP connection manager]
// HTTP connection manager for use in Envoy mobile.
// [#extension: envoy.filters.network.envoy_mobile_http_connection_manager]
message EnvoyMobileHttpConnectionManager {
// The configuration for the underlying HttpConnectionManager which will be
// instantiated for Envoy mobile.

@ -993,6 +993,7 @@ message RequestIDExtension {
// [#protodoc-title: Envoy Mobile HTTP connection manager]
// HTTP connection manager for use in Envoy mobile.
// [#extension: envoy.filters.network.envoy_mobile_http_connection_manager]
message EnvoyMobileHttpConnectionManager {
option (udpa.annotations.versioning).previous_message_type =
"envoy.extensions.filters.network.http_connection_manager.v3."

Loading…
Cancel
Save