Make actual_lrp port mapping keys consistent

This is a follow up commit to: - #64 - e9001b4 In the original PR we accidentally modified a file that is automatically generated from the proto definition instead of modifying the proto defintion itself. [#183842469](https://www.pivotaltracker.com/story/show/183842469) Signed-off-by: David Sabeti <sabetid@vmware.com>
cloudfoundry · Aug 8, 2023 · d58365d · d58365d
1 parent 02f26c7
commit d58365d
Show file tree

Hide file tree

Showing 2 changed files with 78 additions and 77 deletions.
diff --git a/models/actual_lrp.pb.go b/models/actual_lrp.pb.go
diff --git a/models/actual_lrp.proto b/models/actual_lrp.proto
@@ -16,8 +16,8 @@ message ActualLRPGroup {
 message PortMapping {
   uint32 container_port = 1 [(gogoproto.jsontag) = "container_port"];
   uint32 host_port = 2 [(gogoproto.jsontag) = "host_port"];
-  uint32 container_tls_proxy_port = 3;
-  uint32 host_tls_proxy_port = 4;
+  uint32 container_tls_proxy_port = 3 [(gogoproto.jsontag) = "container_tls_proxy_port"];
+  uint32 host_tls_proxy_port = 4 [(gogoproto.jsontag) = "host_tls_proxy_port"];
 }
 
 message ActualLRPKey {