-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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>
- Loading branch information
Showing
110 changed files
with
2,680 additions
and
1,813 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,21 @@ | ||
syntax = "proto3"; | ||
|
||
import "envoy/service/tap/v2alpha/common.proto"; | ||
import "validate/validate.proto"; | ||
|
||
package envoy.admin.v2alpha; | ||
|
||
option java_outer_classname = "TapProto"; | ||
option java_multiple_files = true; | ||
option java_package = "io.envoyproxy.envoy.admin.v2alpha"; | ||
|
||
import "envoy/service/tap/v2alpha/common.proto"; | ||
|
||
import "validate/validate.proto"; | ||
|
||
// The /tap admin request body that is used to configure an active tap session. | ||
message TapRequest { | ||
// The opaque configuration ID used to match the configuration to a loaded extension. | ||
// A tap extension configures a similar opaque ID that is used to match. | ||
string config_id = 1 [(validate.rules).string.min_bytes = 1]; | ||
string config_id = 1 [(validate.rules).string = {min_bytes: 1}]; | ||
|
||
// The tap configuration to load. | ||
service.tap.v2alpha.TapConfig tap_config = 2 [(validate.rules).message.required = true]; | ||
service.tap.v2alpha.TapConfig tap_config = 2 [(validate.rules).message = {required: true}]; | ||
} |
Oops, something went wrong.