|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
package envoy.api.v2;
|
|
|
|
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
5 years ago
|
|
|
import "envoy/api/v2/discovery.proto";
|
|
|
|
|
|
|
|
import "google/api/annotations.proto";
|
|
|
|
|
|
|
|
import "envoy/annotations/resource.proto";
|
|
|
|
import "udpa/annotations/migrate.proto";
|
|
|
|
|
|
|
|
import public "envoy/api/v2/scoped_route.proto";
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
5 years ago
|
|
|
|
|
|
|
option java_package = "io.envoyproxy.envoy.api.v2";
|
|
|
|
option java_outer_classname = "SrdsProto";
|
|
|
|
option java_multiple_files = true;
|
|
|
|
option java_generic_services = true;
|
|
|
|
option (udpa.annotations.file_migrate).move_to_package = "envoy.service.route.v3";
|
|
|
|
|
|
|
|
// [#protodoc-title: SRDS]
|
|
|
|
// * Routing :ref:`architecture overview <arch_overview_http_routing>`
|
|
|
|
|
|
|
|
// The Scoped Routes Discovery Service (SRDS) API distributes
|
|
|
|
// :ref:`ScopedRouteConfiguration<envoy_api_msg.ScopedRouteConfiguration>`
|
|
|
|
// resources. Each ScopedRouteConfiguration resource represents a "routing
|
|
|
|
// scope" containing a mapping that allows the HTTP connection manager to
|
|
|
|
// dynamically assign a routing table (specified via a
|
|
|
|
// :ref:`RouteConfiguration<envoy_api_msg_RouteConfiguration>` message) to each
|
|
|
|
// HTTP request.
|
|
|
|
service ScopedRoutesDiscoveryService {
|
|
|
|
option (envoy.annotations.resource).type = "envoy.api.v2.ScopedRouteConfiguration";
|
|
|
|
|
|
|
|
rpc StreamScopedRoutes(stream DiscoveryRequest) returns (stream DiscoveryResponse) {
|
|
|
|
}
|
|
|
|
|
|
|
|
rpc DeltaScopedRoutes(stream DeltaDiscoveryRequest) returns (stream DeltaDiscoveryResponse) {
|
|
|
|
}
|
|
|
|
|
|
|
|
rpc FetchScopedRoutes(DiscoveryRequest) returns (DiscoveryResponse) {
|
|
|
|
option (google.api.http).post = "/v2/discovery:scoped-routes";
|
|
|
|
option (google.api.http).body = "*";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// [#not-implemented-hide:] Not configuration. Workaround c++ protobuf issue with importing
|
|
|
|
// services: https://github.com/google/protobuf/issues/4221 and protoxform to upgrade the file.
|
|
|
|
message SrdsDummy {
|
|
|
|
}
|