feat(bigqueryreservation): update the api

#### bigqueryreservation:v1

The following keys were added:
- schemas.Autoscale (Total Keys: 7)
- schemas.CapacityCommitment.properties.edition.type (Total Keys: 1)
- schemas.Reservation.properties.autoscale.$ref (Total Keys: 1)
- schemas.Reservation.properties.edition.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/bigqueryreservation_v1.projects.locations.capacityCommitments.html

@@ -119,6 +119,7 @@ <h3>Method Details</h3>
 { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -149,6 +150,7 @@ <h3>Method Details</h3>
     { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -203,6 +205,7 @@ <h3>Method Details</h3>
     { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -242,6 +245,7 @@ <h3>Method Details</h3>
     { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
       &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
       &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+      &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
       &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
         &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
         &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -303,6 +307,7 @@ <h3>Method Details</h3>
     { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -333,6 +338,7 @@ <h3>Method Details</h3>
 { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -362,6 +368,7 @@ <h3>Method Details</h3>
     { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project.
   &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
   &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
   &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
     &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
     &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -405,6 +412,7 @@ <h3>Method Details</h3>
   &quot;first&quot;: { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project. # First capacity commitment, result of a split.
     &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
     &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+    &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
     &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
       &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
       &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
@@ -424,6 +432,7 @@ <h3>Method Details</h3>
   &quot;second&quot;: { # Capacity commitment is a way to purchase compute capacity for BigQuery jobs (in the form of slots) with some committed period of usage. Annual commitments renew by default. Commitments can be removed after their commitment end time passes. In order to remove annual commitment, its plan needs to be changed to monthly or flex first. A capacity commitment resource exists as a child resource of the admin project. # Second capacity commitment, result of a split.
     &quot;commitmentEndTime&quot;: &quot;A String&quot;, # Output only. The end of the current commitment period. It is applicable only for ACTIVE capacity commitments.
     &quot;commitmentStartTime&quot;: &quot;A String&quot;, # Output only. The start of the current commitment period. It is applicable only for ACTIVE capacity commitments.
+    &quot;edition&quot;: &quot;A String&quot;, # Edition of the capacity commitment.
     &quot;failureStatus&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. For FAILED commitment plan, provides the reason of failure.
       &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
       &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.

docs/dyn/bigqueryreservation_v1.projects.locations.reservations.html

@@ -116,8 +116,13 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A reservation is a mechanism used to guarantee slots to users.
+  &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+    &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+    &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+  },
   &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
   &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
   &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
   &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
   &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.
@@ -135,8 +140,13 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A reservation is a mechanism used to guarantee slots to users.
+  &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+    &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+    &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+  },
   &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
   &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
   &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
   &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
   &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.
@@ -178,8 +188,13 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A reservation is a mechanism used to guarantee slots to users.
+  &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+    &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+    &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+  },
   &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
   &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
   &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
   &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
   &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.
@@ -208,8 +223,13 @@ <h3>Method Details</h3>
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Token to retrieve the next page of results, or empty if there are no more results in the list.
   &quot;reservations&quot;: [ # List of reservations visible to the user.
     { # A reservation is a mechanism used to guarantee slots to users.
+      &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+        &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+        &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+      },
       &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
       &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+      &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
       &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
       &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
       &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.
@@ -244,8 +264,13 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A reservation is a mechanism used to guarantee slots to users.
+  &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+    &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+    &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+  },
   &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
   &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
   &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
   &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
   &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.
@@ -263,8 +288,13 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A reservation is a mechanism used to guarantee slots to users.
+  &quot;autoscale&quot;: { # Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won&#x27;t be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won&#x27;t be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature. # The configuration parameters for the auto scaling feature. Note this is an alpha feature.
+    &quot;currentSlots&quot;: &quot;A String&quot;, # Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].
+    &quot;maxSlots&quot;: &quot;A String&quot;, # Number of slots to be scaled when needed.
+  },
   &quot;concurrency&quot;: &quot;A String&quot;, # Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.
   &quot;creationTime&quot;: &quot;A String&quot;, # Output only. Creation time of the reservation.
+  &quot;edition&quot;: &quot;A String&quot;, # Edition of the reservation.
   &quot;ignoreIdleSlots&quot;: True or False, # If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.
   &quot;multiRegionAuxiliary&quot;: True or False, # Applicable only for reservations located within one of the BigQuery multi-regions (US or EU). If set to true, this reservation is placed in the organization&#x27;s secondary region which is designated for disaster recovery purposes. If false, this reservation is placed in the organization&#x27;s default region.
   &quot;name&quot;: &quot;A String&quot;, # The resource name of the reservation, e.g., `projects/*/locations/*/reservations/team1-prod`. The reservation_id must only contain lower case alphanumeric characters or dashes. It must start with a letter and must not end with a dash. Its maximum length is 64 characters.

googleapiclient/discovery_cache/documents/bigqueryreservation.v1.json

@@ -823,7 +823,7 @@
       }
     }
   },
-  "revision": "20230117",
+  "revision": "20230121",
   "rootUrl": "https://bigqueryreservation.googleapis.com/",
   "schemas": {
     "Assignment": {
@@ -875,6 +875,24 @@
       },
       "type": "object"
     },
+    "Autoscale": {
+      "description": "Auto scaling settings. max_slots and budget are mutually exclusive. If max_slots is set: * The system will create a dedicated `FLEX` capacity commitment to hold the slots for auto-scale. Users won't be able to manage it, to avoid conflicts. * Scale-up will happen if there are always pending tasks for the past 10 minutes. * Scale-down will happen, if the system detects that scale-up won't be triggered again. If budget is set: * The system will try to use more slots immediately. * At a particular moment, the number of slots scaled is determined by the sytsem, based on the remaining budget and system limit. But overall the usage will conform to the budget if there is enough traffic. * The system will round the slot usage every minute. **Note** this is an alpha feature.",
+      "id": "Autoscale",
+      "properties": {
+        "currentSlots": {
+          "description": "Output only. The slot capacity added to this reservation when autoscale happens. Will be between [0, max_slots].",
+          "format": "int64",
+          "readOnly": true,
+          "type": "string"
+        },
+        "maxSlots": {
+          "description": "Number of slots to be scaled when needed.",
+          "format": "int64",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "BiReservation": {
       "description": "Represents a BI Reservation.",
       "id": "BiReservation",
@@ -920,6 +938,18 @@
           "readOnly": true,
           "type": "string"
         },
+        "edition": {
+          "description": "Edition of the capacity commitment.",
+          "enum": [
+            "EDITION_UNSPECIFIED",
+            "ENTERPRISE"
+          ],
+          "enumDescriptions": [
+            "Default value, only for legacy reservations and capacity commitments.",
+            "Enterprise edition."
+          ],
+          "type": "string"
+        },
         "failureStatus": {
           "$ref": "Status",
           "description": "Output only. For FAILED commitment plan, provides the reason of failure.",
@@ -941,14 +971,16 @@
             "FLEX",
             "TRIAL",
             "MONTHLY",
-            "ANNUAL"
+            "ANNUAL",
+            "NONE"
           ],
           "enumDescriptions": [
             "Invalid plan value. Requests with this value will be rejected with error code `google.rpc.Code.INVALID_ARGUMENT`.",
             "Flex commitments have committed period of 1 minute after becoming ACTIVE. After that, they are not in a committed period anymore and can be removed any time.",
             "Trial commitments have a committed period of 182 days after becoming ACTIVE. After that, they are converted to a new commitment based on the `renewal_plan`. Default `renewal_plan` for Trial commitment is Flex so that it can be deleted right after committed period ends.",
             "Monthly commitments have a committed period of 30 days after becoming ACTIVE. After that, they are not in a committed period anymore and can be removed any time.",
-            "Annual commitments have a committed period of 365 days after becoming ACTIVE. After that they are converted to a new commitment based on the renewal_plan."
+            "Annual commitments have a committed period of 365 days after becoming ACTIVE. After that they are converted to a new commitment based on the renewal_plan.",
+            "Should only be used for `renewal_plan` and is only meaningful if edition is specified to values other than EDITION_UNSPECIFIED. Otherwise CreateCapacityCommitmentRequest or UpdateCapacityCommitmentRequest will be rejected with error code `google.rpc.Code.INVALID_ARGUMENT`. If the renewal_plan is NONE, capacity commitment will be removed at the end of its commitment period."
           ],
           "type": "string"
         },
@@ -959,14 +991,16 @@
             "FLEX",
             "TRIAL",
             "MONTHLY",
-            "ANNUAL"
+            "ANNUAL",
+            "NONE"
           ],
           "enumDescriptions": [
             "Invalid plan value. Requests with this value will be rejected with error code `google.rpc.Code.INVALID_ARGUMENT`.",
             "Flex commitments have committed period of 1 minute after becoming ACTIVE. After that, they are not in a committed period anymore and can be removed any time.",
             "Trial commitments have a committed period of 182 days after becoming ACTIVE. After that, they are converted to a new commitment based on the `renewal_plan`. Default `renewal_plan` for Trial commitment is Flex so that it can be deleted right after committed period ends.",
             "Monthly commitments have a committed period of 30 days after becoming ACTIVE. After that, they are not in a committed period anymore and can be removed any time.",
-            "Annual commitments have a committed period of 365 days after becoming ACTIVE. After that they are converted to a new commitment based on the renewal_plan."
+            "Annual commitments have a committed period of 365 days after becoming ACTIVE. After that they are converted to a new commitment based on the renewal_plan.",
+            "Should only be used for `renewal_plan` and is only meaningful if edition is specified to values other than EDITION_UNSPECIFIED. Otherwise CreateCapacityCommitmentRequest or UpdateCapacityCommitmentRequest will be rejected with error code `google.rpc.Code.INVALID_ARGUMENT`. If the renewal_plan is NONE, capacity commitment will be removed at the end of its commitment period."
           ],
           "type": "string"
         },
@@ -1084,6 +1118,10 @@
       "description": "A reservation is a mechanism used to guarantee slots to users.",
       "id": "Reservation",
       "properties": {
+        "autoscale": {
+          "$ref": "Autoscale",
+          "description": "The configuration parameters for the auto scaling feature. Note this is an alpha feature."
+        },
         "concurrency": {
           "description": "Job concurrency target which sets a soft upper bound on the number of jobs that can run concurrently in this reservation. This is a soft target due to asynchronous nature of the system and various optimizations for small queries. Default value is 0 which means that concurrency target will be automatically computed by the system. NOTE: this field is exposed as `target_job_concurrency` in the Information Schema, DDL and BQ CLI.",
           "format": "int64",
@@ -1095,6 +1133,18 @@
           "readOnly": true,
           "type": "string"
         },
+        "edition": {
+          "description": "Edition of the reservation.",
+          "enum": [
+            "EDITION_UNSPECIFIED",
+            "ENTERPRISE"
+          ],
+          "enumDescriptions": [
+            "Default value, only for legacy reservations and capacity commitments.",
+            "Enterprise edition."
+          ],
+          "type": "string"
+        },
         "ignoreIdleSlots": {
           "description": "If false, any query or pipeline job using this reservation will use idle slots from other reservations within the same admin project. If true, a query or pipeline job using this reservation will execute with the slot capacity specified in the slot_capacity field at most.",
           "type": "boolean"