|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
package envoy.data.tap.v2alpha;
|
|
|
|
|
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/data/tap/v2alpha/http.proto";
|
|
|
|
import "envoy/data/tap/v2alpha/transport.proto";
|
|
|
|
|
|
|
|
import "udpa/annotations/status.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
|
|
|
import "validate/validate.proto";
|
|
|
|
|
|
|
|
option java_package = "io.envoyproxy.envoy.data.tap.v2alpha";
|
|
|
|
option java_outer_classname = "WrapperProto";
|
|
|
|
option java_multiple_files = true;
|
|
|
|
option go_package = "github.com/envoyproxy/go-control-plane/envoy/data/tap/v2alpha";
|
|
|
|
option (udpa.annotations.file_status).package_version_status = FROZEN;
|
|
|
|
|
|
|
|
// [#protodoc-title: Tap data wrappers]
|
|
|
|
|
|
|
|
// Wrapper for all fully buffered and streamed tap traces that Envoy emits. This is required for
|
|
|
|
// sending traces over gRPC APIs or more easily persisting binary messages to files.
|
|
|
|
message TraceWrapper {
|
|
|
|
oneof trace {
|
|
|
|
option (validate.required) = true;
|
|
|
|
|
|
|
|
// An HTTP buffered tap trace.
|
|
|
|
HttpBufferedTrace http_buffered_trace = 1;
|
|
|
|
|
|
|
|
// An HTTP streamed tap trace segment.
|
|
|
|
HttpStreamedTraceSegment http_streamed_trace_segment = 2;
|
|
|
|
|
|
|
|
// A socket buffered tap trace.
|
|
|
|
SocketBufferedTrace socket_buffered_trace = 3;
|
|
|
|
|
|
|
|
// A socket streamed tap trace segment.
|
|
|
|
SocketStreamedTraceSegment socket_streamed_trace_segment = 4;
|
|
|
|
}
|
|
|
|
}
|