instance.rb in google-cloud-bigtable-admin-v2-0.25.0

- old
+ new

@@ -273,10 +273,14 @@
           #     The priority of requests sent using this app profile.
           # @!attribute [rw] standard_isolation
           #   @return [::Google::Cloud::Bigtable::Admin::V2::AppProfile::StandardIsolation]
           #     The standard options used for isolating this app profile's traffic from
           #     other use cases.
+          # @!attribute [rw] data_boost_isolation_read_only
+          #   @return [::Google::Cloud::Bigtable::Admin::V2::AppProfile::DataBoostIsolationReadOnly]
+          #     Specifies that this app profile is intended for read-only usage via the
+          #     Data Boost feature.
           class AppProfile
             include ::Google::Protobuf::MessageExts
             extend ::Google::Protobuf::MessageExts::ClassMethods
 
             # Read/write requests are routed to the nearest cluster in the instance, and
@@ -315,9 +319,41 @@
             #   @return [::Google::Cloud::Bigtable::Admin::V2::AppProfile::Priority]
             #     The priority of requests sent using this app profile.
             class StandardIsolation
               include ::Google::Protobuf::MessageExts
               extend ::Google::Protobuf::MessageExts::ClassMethods
+            end
+
+            # Data Boost is a serverless compute capability that lets you run
+            # high-throughput read jobs on your Bigtable data, without impacting the
+            # performance of the clusters that handle your application traffic.
+            # Currently, Data Boost exclusively supports read-only use-cases with
+            # single-cluster routing.
+            #
+            # Data Boost reads are only guaranteed to see the results of writes that
+            # were written at least 30 minutes ago. This means newly written values may
+            # not become visible for up to 30m, and also means that old values may
+            # remain visible for up to 30m after being deleted or overwritten. To
+            # mitigate the staleness of the data, users may either wait 30m, or use
+            # CheckConsistency.
+            # @!attribute [rw] compute_billing_owner
+            #   @return [::Google::Cloud::Bigtable::Admin::V2::AppProfile::DataBoostIsolationReadOnly::ComputeBillingOwner]
+            #     The Compute Billing Owner for this Data Boost App Profile.
+            class DataBoostIsolationReadOnly
+              include ::Google::Protobuf::MessageExts
+              extend ::Google::Protobuf::MessageExts::ClassMethods
+
+              # Compute Billing Owner specifies how usage should be accounted when using
+              # Data Boost. Compute Billing Owner also configures which Cloud Project is
+              # charged for relevant quota.
+              module ComputeBillingOwner
+                # Unspecified value.
+                COMPUTE_BILLING_OWNER_UNSPECIFIED = 0
+
+                # The host Cloud Project containing the targeted Bigtable Instance /
+                # Table pays for compute.
+                HOST_PAYS = 1
+              end
             end
 
             # Possible priorities for an app profile. Note that higher priority writes
             # can sometimes queue behind lower priority writes to the same tablet, as
             # writes must be strictly sequenced in the durability log.