api: add oneof to support a future named resource

Signed-off-by: Sanjay Pujare <sanjaypujare@users.noreply.github.com>
envoyproxy · May 19, 2020 · 71b3508 · 71b3508
1 parent d09a366
commit 71b3508
Show file tree

Hide file tree

Showing 4 changed files with 16 additions and 4 deletions.
diff --git a/api/envoy/extensions/transport_sockets/tls/v3/tls.proto b/api/envoy/extensions/transport_sockets/tls/v3/tls.proto
@@ -115,7 +115,10 @@ message CommonTlsContext {
     // to maintain a single certificate-provider instance. The sharing can happen, for
     // example, among multiple clusters or between the tls_certificate and validation_context
     // certificate providers of a cluster.
-    config.core.v3.TypedExtensionConfig typed_config = 2;
+    oneof config {
+      // This config could be supplied inline or it could be a named xDS resource (in future).
+      config.core.v3.TypedExtensionConfig typed_config = 2;
+    }
   }
 
   message CombinedCertificateValidationContext {

diff --git a/api/envoy/extensions/transport_sockets/tls/v4alpha/tls.proto b/api/envoy/extensions/transport_sockets/tls/v4alpha/tls.proto
@@ -118,7 +118,10 @@ message CommonTlsContext {
     // to maintain a single certificate-provider instance. The sharing can happen, for
     // example, among multiple clusters or between the tls_certificate and validation_context
     // certificate providers of a cluster.
-    config.core.v4alpha.TypedExtensionConfig typed_config = 2;
+    oneof config {
+      // This config could be supplied inline or it could be a named xDS resource (in future).
+      config.core.v4alpha.TypedExtensionConfig typed_config = 2;
+    }
   }
 
   message CombinedCertificateValidationContext {

diff --git a/generated_api_shadow/envoy/extensions/transport_sockets/tls/v3/tls.proto b/generated_api_shadow/envoy/extensions/transport_sockets/tls/v3/tls.proto
diff --git a/generated_api_shadow/envoy/extensions/transport_sockets/tls/v4alpha/tls.proto b/generated_api_shadow/envoy/extensions/transport_sockets/tls/v4alpha/tls.proto