laying groundwork for dynamic updates via protos

PeerDB-io · Jan 3, 2024 · ecc91d8 · ecc91d8
1 parent 4b0bba1
commit ecc91d8
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 7 deletions.
diff --git a/protos/flow.proto b/protos/flow.proto
@@ -419,3 +419,16 @@ enum FlowStatus {
   // neither button should be enabled
   STATUS_TERMINATED = 7;
 }
+
+message CDCFlowStateUpdate {
+}
+
+message QRepFlowStateUpdate  {
+}
+
+message FlowStateUpdate {
+  oneof update {
+    CDCFlowStateUpdate cdc_flow_state_update = 1;
+    QRepFlowStateUpdate qrep_flow_state_update = 2;
+  }
+}
diff --git a/protos/route.proto b/protos/route.proto
@@ -182,18 +182,13 @@ message MirrorStatusResponse {
   peerdb_flow.FlowStatus current_flow_state = 5;
 }
 
-// in the future, consider moving DropFlow to this and reduce route surface
-enum FlowState {
-  STATE_UNKNOWN = 0;
-  STATE_RUNNING = 1;
-  STATE_PAUSED = 2;
-}
-
 message FlowStateChangeRequest {
   string flow_job_name = 1;
   peerdb_flow.FlowStatus requested_flow_state = 2;
   peerdb_peers.Peer source_peer = 3;
   peerdb_peers.Peer destination_peer = 4;
+  // only can be sent in certain situations
+  peerdb_flow.FlowStateUpdate flow_state_update = 5;
 }
 
 message FlowStateChangeResponse {