|
|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
|
|
package envoy.config.common.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/api/v2/core/config_source.proto";
|
|
|
|
|
import "envoy/service/tap/v2alpha/common.proto";
|
|
|
|
|
|
|
|
|
|
import "udpa/annotations/migrate.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.config.common.tap.v2alpha";
|
|
|
|
|
option java_outer_classname = "CommonProto";
|
|
|
|
|
option java_multiple_files = true;
|
|
|
|
|
option (udpa.annotations.file_migrate).move_to_package = "envoy.extensions.common.tap.v3";
|
|
|
|
|
|
|
|
|
|
// [#protodoc-title: Common tap extension configuration]
|
|
|
|
|
|
|
|
|
|
// Common configuration for all tap extensions.
|
|
|
|
|
message CommonExtensionConfig {
|
|
|
|
|
// [#not-implemented-hide:]
|
|
|
|
|
message TapDSConfig {
|
|
|
|
|
// Configuration for the source of TapDS updates for this Cluster.
|
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
|
|
|
api.v2.core.ConfigSource config_source = 1 [(validate.rules).message = {required: true}];
|
|
|
|
|
|
|
|
|
|
// Tap config to request from XDS server.
|
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
|
|
|
string name = 2 [(validate.rules).string = {min_bytes: 1}];
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
oneof config_type {
|
|
|
|
|
option (validate.required) = true;
|
|
|
|
|
|
|
|
|
|
// If specified, the tap filter will be configured via an admin handler.
|
|
|
|
|
AdminConfig admin_config = 1;
|
|
|
|
|
|
|
|
|
|
// If specified, the tap filter will be configured via a static configuration that cannot be
|
|
|
|
|
// changed.
|
|
|
|
|
service.tap.v2alpha.TapConfig static_config = 2;
|
|
|
|
|
|
|
|
|
|
// [#not-implemented-hide:] Configuration to use for TapDS updates for the filter.
|
|
|
|
|
TapDSConfig tapds_config = 3;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// Configuration for the admin handler. See :ref:`here <config_http_filters_tap_admin_handler>` for
|
|
|
|
|
// more information.
|
|
|
|
|
message AdminConfig {
|
|
|
|
|
// Opaque configuration ID. When requests are made to the admin handler, the passed opaque ID is
|
|
|
|
|
// matched to the configured filter opaque ID to determine which filter to configure.
|
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
|
|
|
string config_id = 1 [(validate.rules).string = {min_bytes: 1}];
|
|
|
|
|
}
|
