treewide: Fix RPC_REQUEST_STANDARD_NAME and RPC_RESPONSE_STANDARD_NAME
Change-Id: I190ade92c04313961edd4787196568216d028ba8
Reviewed-on: https://review.monogon.dev/c/monogon/+/3818
Tested-by: Jenkins CI
Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
diff --git a/cloud/bmaas/server/api/agent.proto b/cloud/bmaas/server/api/agent.proto
index 5bebef5..67ec4a3 100644
--- a/cloud/bmaas/server/api/agent.proto
+++ b/cloud/bmaas/server/api/agent.proto
@@ -17,7 +17,7 @@
// isn't reactive, so it would have to do its own inner polling to create
// a stream of updates. To keep things simple, we instead let the agent decide
// on the cadence of updates it wants to keep up with.
- rpc Heartbeat(AgentHeartbeatRequest) returns (AgentHeartbeatResponse);
+ rpc Heartbeat(HeartbeatRequest) returns (HeartbeatResponse);
}
message AgentHardwareReport {
@@ -50,7 +50,7 @@
}
}
-message AgentHeartbeatRequest {
+message HeartbeatRequest {
// MachineID that this agent represents. Technically not necessary since
// keypairs between agents should be unique, but this provides an extra layer
// of protection against programming bugs.
@@ -90,7 +90,7 @@
}
}
-message AgentHeartbeatResponse {
+message HeartbeatResponse {
// If set, the control plane is requesting the installation of an operating
// system.
OSInstallationRequest installation_request = 1;