1syntax = "proto3";
2
3package envoy.service.discovery.v3;
4
5import "envoy/service/discovery/v3/discovery.proto";
6
7import "udpa/annotations/status.proto";
8import "udpa/annotations/versioning.proto";
9
10option java_package = "io.envoyproxy.envoy.service.discovery.v3";
11option java_outer_classname = "AdsProto";
12option java_multiple_files = true;
13option java_generic_services = true;
14option (udpa.annotations.file_status).package_version_status = ACTIVE;
15
16// [#protodoc-title: Aggregated Discovery Service (ADS)]
17
18// [#not-implemented-hide:] Discovery services for endpoints, clusters, routes,
19// and listeners are retained in the package `envoy.api.v2` for backwards
20// compatibility with existing management servers. New development in discovery
21// services should proceed in the package `envoy.service.discovery.v2`.
22
23// See https://github.com/lyft/envoy-api#apis for a description of the role of
24// ADS and how it is intended to be used by a management server. ADS requests
25// have the same structure as their singleton xDS counterparts, but can
26// multiplex many resource types on a single stream. The type_url in the
27// DiscoveryRequest/DiscoveryResponse provides sufficient information to recover
28// the multiplexed singleton APIs at the Envoy instance and management server.
29service AggregatedDiscoveryService {
30 // This is a gRPC-only API.
31 rpc StreamAggregatedResources(stream DiscoveryRequest) returns (stream DiscoveryResponse) {
32 }
33
34 rpc DeltaAggregatedResources(stream DeltaDiscoveryRequest)
35 returns (stream DeltaDiscoveryResponse) {
36 }
37}
38
39// [#not-implemented-hide:] Not configuration. Workaround c++ protobuf issue with importing
40// services: https://github.com/google/protobuf/issues/4221
41message AdsDummy {
42 option (udpa.annotations.versioning).previous_message_type =
43 "envoy.service.discovery.v2.AdsDummy";
44}
View as plain text