feat: Add a new field soft_failover_start_time in the existing replication_status in .google.cloud.bigquery.reservation.v1.Reservation to provide visibility into the state of ongoing soft failover operations on the reservation

Google APIs · copybara-github · commit afe86f35d153 · 2025-09-02T10:02:55.000-07:00
feat: Add a new field `failover_mode` to `.google.cloud.bigquery.reservation.v1.FailoverReservationRequest` that allows users to choose between the HARD or SOFT failover modes when they initiate a failover operation on a reservation

PiperOrigin-RevId: 802187284
diff --git a/google/cloud/bigquery/reservation/v1/reservation.proto b/google/cloud/bigquery/reservation/v1/reservation.proto
@@ -496,6 +496,14 @@ message Reservation {
     // that was successfully replicated to the secondary.
     google.protobuf.Timestamp last_replication_time = 3
         [(google.api.field_behavior) = OUTPUT_ONLY];
+
+    // Output only. The time at which a soft failover for the reservation and
+    // its associated datasets was initiated. After this field is set, all
+    // subsequent changes to the reservation will be rejected unless a hard
+    // failover overrides this operation. This field will be cleared once the
+    // failover is complete.
+    google.protobuf.Timestamp soft_failover_start_time = 4
+        [(google.api.field_behavior) = OUTPUT_ONLY];
   }
 
   // The resource name of the reservation, e.g.,
@@ -895,6 +903,11 @@ message FailoverReservationRequest {
       type: "bigqueryreservation.googleapis.com/Reservation"
     }
   ];
+
+  // Optional. A parameter that determines how writes that are pending
+  // replication are handled after a failover is initiated. If not specified,
+  // HARD failover mode is used by default.
+  FailoverMode failover_mode = 2 [(google.api.field_behavior) = OPTIONAL];
 }
 
 // The request for
@@ -1389,3 +1402,21 @@ enum Edition {
   // Enterprise Plus edition.
   ENTERPRISE_PLUS = 3;
 }
+
+// The failover mode when a user initiates a failover on a reservation
+// determines how writes that arepending replication are handled after the
+// failover is initiated.
+enum FailoverMode {
+  // Invalid value.
+  FAILOVER_MODE_UNSPECIFIED = 0;
+
+  // When customers initiate a soft failover, BigQuery will wait until all
+  // committed writes are replicated to the secondary. This mode requires both
+  // regions to be available for the failover to succeed and prevents data loss.
+  SOFT = 1;
+
+  // When customers initiate a hard failover, BigQuery will not wait until all
+  // committed writes are replicated to the secondary. There can be data loss
+  // for hard failover.
+  HARD = 2;
+}
