feat(dataproc)!: update the API

BREAKING CHANGE: This release has breaking changes.

#### dataproc:v1

The following keys were deleted:
- schemas.UsageMetrics.properties.milliSlotSeconds.description
- schemas.UsageMetrics.properties.milliSlotSeconds.format
- schemas.UsageMetrics.properties.milliSlotSeconds.type
- schemas.UsageSnapshot.properties.milliSlot.description
- schemas.UsageSnapshot.properties.milliSlot.format
- schemas.UsageSnapshot.properties.milliSlot.type

The following keys were added:
- schemas.RepairClusterRequest.properties.dataprocSuperUser.description
- schemas.RepairClusterRequest.properties.dataprocSuperUser.type

Author: yoshi-automation

discovery/dataproc-v1.json

@@ -5012,7 +5012,7 @@
       }
     }
   },
-  "revision": "20250930",
+  "revision": "20251001",
   "rootUrl": "https://dataproc.googleapis.com/",
   "schemas": {
     "AcceleratorConfig": {
@@ -9619,6 +9619,10 @@
           "description": "Optional. Specifying the cluster_uuid means the RPC will fail (with error NOT_FOUND) if a cluster with the specified UUID does not exist.",
           "type": "string"
         },
+        "dataprocSuperUser": {
+          "description": "Optional. Whether the request is submitted by Dataproc super user. If true, IAM will check 'dataproc.clusters.repair' permission instead of 'dataproc.clusters.update' permission. This is to give Dataproc superuser the ability to repair clusters without granting the overly broad update permission.",
+          "type": "boolean"
+        },
         "gracefulDecommissionTimeout": {
           "description": "Optional. Timeout for graceful YARN decommissioning. Graceful decommissioning facilitates the removal of cluster nodes without interrupting jobs in progress. The timeout specifies the amount of time to wait for jobs finish before forcefully removing nodes. The default timeout is 0 for forceful decommissioning, and the maximum timeout period is 1 day. (see JSON Mapping—Duration (https://developers.google.com/protocol-buffers/docs/proto3#json)).graceful_decommission_timeout is supported in Dataproc image versions 1.2+.",
           "format": "google-duration",
@@ -12600,11 +12604,6 @@
           "format": "int64",
           "type": "string"
         },
-        "milliSlotSeconds": {
-          "description": "Optional. Slot usage in (milliSlot x seconds).",
-          "format": "int64",
-          "type": "string"
-        },
         "shuffleStorageGbSeconds": {
           "description": "Optional. Shuffle storage usage in (GB x seconds) (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing)).",
           "format": "int64",
@@ -12641,11 +12640,6 @@
           "format": "int64",
           "type": "string"
         },
-        "milliSlot": {
-          "description": "Optional. Milli (one-thousandth) Slot usage of the workload.",
-          "format": "int64",
-          "type": "string"
-        },
         "shuffleStorageGb": {
           "description": "Optional. Shuffle Storage in gigabytes (GB). (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing))",
           "format": "int64",

src/apis/dataproc/v1.ts

@@ -2877,6 +2877,10 @@ export namespace dataproc_v1 {
      * Optional. Specifying the cluster_uuid means the RPC will fail (with error NOT_FOUND) if a cluster with the specified UUID does not exist.
      */
     clusterUuid?: string | null;
+    /**
+     * Optional. Whether the request is submitted by Dataproc super user. If true, IAM will check 'dataproc.clusters.repair' permission instead of 'dataproc.clusters.update' permission. This is to give Dataproc superuser the ability to repair clusters without granting the overly broad update permission.
+     */
+    dataprocSuperUser?: boolean | null;
     /**
      * Optional. Timeout for graceful YARN decommissioning. Graceful decommissioning facilitates the removal of cluster nodes without interrupting jobs in progress. The timeout specifies the amount of time to wait for jobs finish before forcefully removing nodes. The default timeout is 0 for forceful decommissioning, and the maximum timeout period is 1 day. (see JSON Mapping—Duration (https://developers.google.com/protocol-buffers/docs/proto3#json)).graceful_decommission_timeout is supported in Dataproc image versions 1.2+.
      */
@@ -4412,10 +4416,6 @@ export namespace dataproc_v1 {
      * Optional. DCU (Dataproc Compute Units) usage in (milliDCU x seconds) (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing)).
      */
     milliDcuSeconds?: string | null;
-    /**
-     * Optional. Slot usage in (milliSlot x seconds).
-     */
-    milliSlotSeconds?: string | null;
     /**
      * Optional. Shuffle storage usage in (GB x seconds) (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing)).
      */
@@ -4445,10 +4445,6 @@ export namespace dataproc_v1 {
      * Optional. Milli (one-thousandth) Dataproc Compute Units (DCUs) charged at premium tier (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing)).
      */
     milliDcuPremium?: string | null;
-    /**
-     * Optional. Milli (one-thousandth) Slot usage of the workload.
-     */
-    milliSlot?: string | null;
     /**
      * Optional. Shuffle Storage in gigabytes (GB). (see Dataproc Serverless pricing (https://cloud.google.com/dataproc-serverless/pricing))
      */
@@ -20485,6 +20481,7 @@ export namespace dataproc_v1 {
      *       // {
      *       //   "cluster": {},
      *       //   "clusterUuid": "my_clusterUuid",
+     *       //   "dataprocSuperUser": false,
      *       //   "gracefulDecommissionTimeout": "my_gracefulDecommissionTimeout",
      *       //   "nodePools": [],
      *       //   "parentOperationId": "my_parentOperationId",