An update to Go gRPC Protobuf generation will change service registration function signatures to use an interface instead of a concrete type in generated .pb.go service files. This change should affect very few client library users. See release notes advisories in https://github.com/googleapis/google-cloud-go/pull/11025.
PiperOrigin-RevId: 817247116
feat: Add support for creation and modification of new reservation groups
feat: Add new reservation IAM policy get/set/test methods
PiperOrigin-RevId: 814816863
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
feat: Add Reservation.scaling_mode field and its corresponding enum message ScalingMode. This field should be used together with Reservation.max_slots
PiperOrigin-RevId: 795606766
feat: Add the CONTINUOUS Job type to `.google.cloud.bigquery.reservation.v1.Assignment.JobType` for continuous SQL jobs
feat: Add a new field `enable_gemini_in_bigquery` to `.google.cloud.bigquery.reservation.v1.Assignment` that indicates if "Gemini in Bigquery"(https://cloud.google.com/gemini/docs/bigquery/overview) features are enabled for the reservation assignment
docs: Update the `google.api.field_behavior` for the `.google.cloud.bigquery.reservation.v1.Reservation.primary_location` and `.google.cloud.bigquery.reservation.v1.Reservation.original_primary_location` fields to clarify that they are `OUTPUT_ONLY`
docs: Remove the section about `EDITION_UNSPECIFIED` in the comment for `slot_capacity` in `.google.cloud.bigquery.reservation.v1.Reservation` to clarify that
PiperOrigin-RevId: 731341086
feat: Add a new field `is_flat_rate` to `.google.cloud.bigquery.reservation.v1.CapacityCommitment` to distinguish between flat rate and edition commitments
docs: Clarify that `Autoscale.current_slots` in message `.google.cloud.bigquery.reservation.v1.Reservation` can temporarily be larger than `Autoscale.max_slots` if users reduce `Autoscale.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 slots
docs: Update comments for `commitment_start_time` and `commitment_end_time` in message `.google.cloud.bigquery.reservation.v1.CapacityCommitment` to provide details on how these values are affected by commitment renewal
PiperOrigin-RevId: 702079972
chore: disallow "transport=rest" for services where numeric enums are not confirmed to be supported (except in PHP and Java)
PiperOrigin-RevId: 493113566
feat: Reservation objects now contain a creation time and an update time
feat: Added commitment_start_time to capacity commitments
feat: Force deleting capacity commitments is allowed while reservations with active assignments exist
feat: ML_EXTERNAL job type is supported
feat: Optional id can be passed into CreateCapacityCommitment and CreateAssignment
docs: Clarified docs for None assignments
fix!: Fixed pattern for BiReservation object
BREAKING_CHANGE: Changed from `bireservation` to `biReservation`
PiperOrigin-RevId: 394129271
