Skip to content

Commit 1959a32

Browse files
committed
add explicit UNSPECIFFIED tm policy
it turns out there is no way to check if it was specified or not server side, being an enum.
1 parent c6628ab commit 1959a32

File tree

2 files changed

+45
-40
lines changed

2 files changed

+45
-40
lines changed

go-routesapi/routes.pb.go

Lines changed: 41 additions & 37 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

routes.proto

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ message BaselineWorkload {
8282
message WorkloadPortMapping {
8383
uint32 workload_port = 1;
8484
repeated Location destinations = 2;
85-
// TrafficManagery specification, used to specify how to interact with
85+
// TrafficManager specification, used to specify how to interact with
8686
// the TM. If absent, no traffic goes to TM. If present, some traffic
8787
// may go to TM.
8888
TrafficManager traffic_manager = 3;
@@ -162,8 +162,9 @@ message WorkloadRoutingRulesRequest {
162162
// TrafficManagerPolicy indicates the policy used to determine whether
163163
// or not to use the traffic manager for sandbox traffic.
164164
enum TrafficManagerPolicy {
165-
HEADER = 0;
166-
ALL = 1;
165+
UNSPECIFIED = 0;
166+
HEADER = 1;
167+
ALL = 2;
167168
}
168169

169170
// ClientInfo indicates what capabilities the client has. If absent,

0 commit comments

Comments
 (0)