chore: update types from Discovery (#1476)

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

Author: yoshi-code-bot

src/types.d.ts

@@ -13,7 +13,7 @@
 // limitations under the License.
 
 /**
- * Discovery Revision: 20250313
+ * Discovery Revision: 20250511
  */
 
 /**
@@ -417,7 +417,7 @@ declare namespace bigquery {
   };
 
   /**
-   * Configuration for BigLake managed tables.
+   * Configuration for BigQuery tables for Apache Iceberg (formerly BigLake managed tables.)
    */
   type IBigLakeConfiguration = {
     /**
@@ -1093,6 +1093,10 @@ declare namespace bigquery {
        * The dataset reference. Use this property to access specific parts of the dataset's ID, such as project ID or dataset ID.
        */
       datasetReference?: IDatasetReference;
+      /**
+       * Output only. Reference to a read-only external dataset defined in data catalogs outside of BigQuery. Filled out when the dataset type is EXTERNAL.
+       */
+      externalDatasetReference?: IExternalDatasetReference;
       /**
        * An alternate name for the dataset. The friendly name is purely decorative in nature.
        */
@@ -2549,7 +2553,7 @@ declare namespace bigquery {
      */
     timePartitioning?: ITimePartitioning;
     /**
-     * Optional. [Experimental] Default time zone that will apply when parsing timestamp values that have no specific time zone.
+     * Optional. Default time zone that will apply when parsing timestamp values that have no specific time zone.
      */
     timeZone?: string;
     /**
@@ -2561,7 +2565,7 @@ declare namespace bigquery {
      */
     useAvroLogicalTypes?: boolean;
     /**
-     * Optional. Specifies the action that occurs if the destination table already exists. The following values are supported: * WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the data, removes the constraints and uses the schema from the load job. * WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. * WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_APPEND. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.
+     * Optional. Specifies the action that occurs if the destination table already exists. The following values are supported: * WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the data, removes the constraints and uses the schema from the load job. * WRITE_TRUNCATE_DATA: If the table already exists, BigQuery overwrites the data, but keeps the constraints and schema of the existing table. * WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. * WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_APPEND. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.
      */
     writeDisposition?: string;
   };
@@ -2675,7 +2679,7 @@ declare namespace bigquery {
      */
     userDefinedFunctionResources?: Array<IUserDefinedFunctionResource>;
     /**
-     * Optional. Specifies the action that occurs if the destination table already exists. The following values are supported: * WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the data, removes the constraints, and uses the schema from the query result. * WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. * WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_EMPTY. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.
+     * Optional. Specifies the action that occurs if the destination table already exists. The following values are supported: * WRITE_TRUNCATE: If the table already exists, BigQuery overwrites the data, removes the constraints, and uses the schema from the query result. * WRITE_TRUNCATE_DATA: If the table already exists, BigQuery overwrites the data, but keeps the constraints and schema of the existing table. * WRITE_APPEND: If the table already exists, BigQuery appends the data to the table. * WRITE_EMPTY: If the table already exists and contains data, a 'duplicate' error is returned in the job result. The default value is WRITE_EMPTY. Each action is atomic and only occurs if BigQuery is able to complete the job successfully. Creation, truncation and append actions occur as one atomic update upon job completion.
      */
     writeDisposition?: string;
     /**
@@ -3055,7 +3059,7 @@ declare namespace bigquery {
      */
     referencedRoutines?: Array<IRoutineReference>;
     /**
-     * Output only. Referenced tables for the job. Queries that reference more than 50 tables will not have a complete list.
+     * Output only. Referenced tables for the job.
      */
     referencedTables?: Array<ITableReference>;
     /**
@@ -4149,6 +4153,10 @@ declare namespace bigquery {
      * Total units of work remaining for the query. This number can be revised (increased or decreased) while the query is running.
      */
     pendingUnits?: string;
+    /**
+     * Total shuffle usage ratio in shuffle RAM per reservation of this query. This will be provided for reservation customers only.
+     */
+    shuffleRamUsageRatio?: number;
     /**
      * Cumulative slot-ms consumed by the query.
      */
@@ -4954,7 +4962,7 @@ declare namespace bigquery {
 
   type ITable = {
     /**
-     * Optional. Specifies the configuration of a BigLake managed table.
+     * Optional. Specifies the configuration of a BigQuery table for Apache Iceberg.
      */
     biglakeConfiguration?: IBigLakeConfiguration;
     /**
@@ -6390,6 +6398,14 @@ declare namespace bigquery {
        * Optional. The version of the provided access policy schema. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. This version refers to the schema version of the access policy and not the version of access policy. This field's value can be equal or more than the access policy schema provided in the request. For example, * Operations updating conditional access policy binding in datasets must specify version 3. Some of the operations are : - Adding a new access policy entry with condition. - Removing an access policy entry with condition. - Updating an access policy entry with condition. * But dataset with no conditional role bindings in access policy may specify any valid value or leave the field unset. If unset or if 0 or 1 value is used for dataset with conditional bindings, request will be rejected. This field will be mapped to IAM Policy version (https://cloud.google.com/iam/docs/policies#versions) and will be used to set policy in IAM.
        */
       accessPolicyVersion?: number;
+      /**
+       * Optional. Specifies the fields of dataset that update/patch operation is targeting By default, both metadata and ACL fields are updated.
+       */
+      updateMode?:
+        | 'UPDATE_MODE_UNSPECIFIED'
+        | 'UPDATE_METADATA'
+        | 'UPDATE_ACL'
+        | 'UPDATE_FULL';
     };
 
     /**
@@ -6400,6 +6416,14 @@ declare namespace bigquery {
        * Optional. The version of the provided access policy schema. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. This version refers to the schema version of the access policy and not the version of access policy. This field's value can be equal or more than the access policy schema provided in the request. For example, * Operations updating conditional access policy binding in datasets must specify version 3. Some of the operations are : - Adding a new access policy entry with condition. - Removing an access policy entry with condition. - Updating an access policy entry with condition. * But dataset with no conditional role bindings in access policy may specify any valid value or leave the field unset. If unset or if 0 or 1 value is used for dataset with conditional bindings, request will be rejected. This field will be mapped to IAM Policy version (https://cloud.google.com/iam/docs/policies#versions) and will be used to set policy in IAM.
        */
       accessPolicyVersion?: number;
+      /**
+       * Optional. Specifies the fields of dataset that update/patch operation is targeting By default, both metadata and ACL fields are updated.
+       */
+      updateMode?:
+        | 'UPDATE_MODE_UNSPECIFIED'
+        | 'UPDATE_METADATA'
+        | 'UPDATE_ACL'
+        | 'UPDATE_FULL';
     };
   }