feat: await/catch promises, and update listOperationsAsync return type

protos/google/bigtable/admin/v2/instance.proto

@@ -172,6 +172,21 @@ message Cluster {
     DISABLED = 4;
   }
 
+  // Possible node scaling factors of the clusters. Node scaling delivers better
+  // latency and more throughput by removing node boundaries.
+  enum NodeScalingFactor {
+    // No node scaling specified. Defaults to NODE_SCALING_FACTOR_1X.
+    NODE_SCALING_FACTOR_UNSPECIFIED = 0;
+
+    // The cluster is running with a scaling factor of 1.
+    NODE_SCALING_FACTOR_1X = 1;
+
+    // The cluster is running with a scaling factor of 2.
+    // All node count values must be in increments of 2 with this scaling factor
+    // enabled, otherwise an INVALID_ARGUMENT error will be returned.
+    NODE_SCALING_FACTOR_2X = 2;
+  }
+
   // Autoscaling config for a cluster.
   message ClusterAutoscalingConfig {
     // Required. Autoscaling limits for this cluster.
@@ -229,6 +244,10 @@ message Cluster {
   // throughput and more consistent performance.
   int32 serve_nodes = 4;
 
+  // Immutable. The node scaling factor of this cluster.
+  NodeScalingFactor node_scaling_factor = 9
+      [(google.api.field_behavior) = IMMUTABLE];
+
   oneof config {
     // Configuration for this cluster.
     ClusterConfig cluster_config = 7;
@@ -258,9 +277,34 @@ message AppProfile {
   // equidistant. Choosing this option sacrifices read-your-writes consistency
   // to improve availability.
   message MultiClusterRoutingUseAny {
+    // If enabled, Bigtable will route the request based on the row key of the
+    // request, rather than randomly. Instead, each row key will be assigned
+    // to a cluster, and will stick to that cluster. If clusters are added or
+    // removed, then this may affect which row keys stick to which clusters.
+    // To avoid this, users can use a cluster group to specify which clusters
+    // are to be used. In this case, new clusters that are not a part of the
+    // cluster group will not be routed to, and routing will be unaffected by
+    // the new cluster. Moreover, clusters specified in the cluster group cannot
+    // be deleted unless removed from the cluster group.
+    message RowAffinity {}
+
     // The set of clusters to route to. The order is ignored; clusters will be
     // tried in order of distance. If left empty, all clusters are eligible.
     repeated string cluster_ids = 1;
+
+    // Possible algorithms for routing affinity. If enabled, Bigtable will
+    // route between equidistant clusters in a deterministic order rather than
+    // choosing randomly.
+    //
+    // This mechanism gives read-your-writes consistency for *most* requests
+    // under *most* circumstances, without sacrificing availability. Consistency
+    // is *not* guaranteed, as requests might still fail over between clusters
+    // in the event of errors or latency.
+    oneof affinity {
+      // Row affinity sticky routing based on the row key of the request.
+      // Requests that span multiple rows are routed non-deterministically.
+      RowAffinity row_affinity = 3;
+    }
   }
 
   // Unconditionally routes all read/write requests to a specific cluster.

protos/google/bigtable/v2/feature_flags.proto

@@ -61,4 +61,10 @@ message FeatureFlags {
 
   // Notify the server that the client has client side metrics enabled.
   bool client_side_metrics_enabled = 8;
+
+  // Notify the server that the client using Traffic Director endpoint.
+  bool traffic_director_enabled = 9;
+
+  // Notify the server that the client explicitly opted in for Direct Access.
+  bool direct_access_requested = 10;
 }