feat: [google-cloud-bigquery-reservation] Add the managed disaster recovery API(https://cloud.google.com/bigquery/docs/managed-disaster-recovery) #13316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BEGIN_COMMIT_OVERRIDE
feat: Add the managed disaster recovery API(https://cloud.google.com/bigquery/docs/managed-disaster-recovery)
feat: Add a new field
is_flat_rate
to.google.cloud.bigquery.reservation.v1.CapacityCommitment
to distinguish between flat rate and edition commitmentsdocs: Clarify that
Autoscale.current_slots
in message.google.cloud.bigquery.reservation.v1.Reservation
can temporarily be larger thanAutoscale.max_slots
if users reduceAutoscale.max_slots
docs: Update comment for
slot_capacity
in message.google.cloud.bigquery.reservation.v1.Reservation
to provide more clarity about reservation baselines, committed slots and autoscaler SKU charges when the baseline exceeds committed slotsdocs: Update comments for
commitment_start_time
andcommitment_end_time
in message.google.cloud.bigquery.reservation.v1.CapacityCommitment
to provide details on how these values are affected by commitment renewalEND_COMMIT_OVERRIDE
feat: Add a new field
is_flat_rate
to.google.cloud.bigquery.reservation.v1.CapacityCommitment
to distinguish between flat rate and edition commitmentsdocs: Clarify that
Autoscale.current_slots
in message.google.cloud.bigquery.reservation.v1.Reservation
can temporarily be larger thanAutoscale.max_slots
if users reduceAutoscale.max_slots
docs: Update comment for
slot_capacity
in message.google.cloud.bigquery.reservation.v1.Reservation
to provide more clarity about reservation baselines, committed slots and autoscaler SKU charges when the baseline exceeds committed slotsdocs: Update comments for
commitment_start_time
andcommitment_end_time
in message.google.cloud.bigquery.reservation.v1.CapacityCommitment
to provide details on how these values are affected by commitment renewalPiperOrigin-RevId: 702079972
Source-Link: googleapis/googleapis@4743cf9
Source-Link: https://github.com/googleapis/googleapis-gen/commit/30e936000bfab99bf2856bb846a50eb0ee0385b7
Copy-Tag: eyJwIjoicGFja2FnZXMvZ29vZ2xlLWNsb3VkLWJpZ3F1ZXJ5LXJlc2VydmF0aW9uLy5Pd2xCb3QueWFtbCIsImgiOiIzMGU5MzYwMDBiZmFiOTliZjI4NTZiYjg0NmE1MGViMGVlMDM4NWI3In0=