feat(all): auto-regenerate discovery clients (#2674)

Author: yoshi-automation

bigtableadmin/v2/bigtableadmin-api.json

@@ -2194,7 +2194,7 @@
       }
     }
   },
-  "revision": "20240604",
+  "revision": "20240628",
   "rootUrl": "https://bigtableadmin.googleapis.com/",
   "schemas": {
     "AppProfile": {
@@ -3189,7 +3189,7 @@
       "type": "object"
     },
     "GoogleBigtableAdminV2TypeBytesEncodingRaw": {
-      "description": "Leaves the value \"as-is\" * Natural sort? Yes * Self-delimiting? No * Compatibility? N/A",
+      "description": "Leaves the value \"as-is\" * Order-preserving? Yes * Self-delimiting? No * Compatibility? N/A",
       "id": "GoogleBigtableAdminV2TypeBytesEncodingRaw",
       "properties": {},
       "type": "object"
@@ -3217,12 +3217,12 @@
       "type": "object"
     },
     "GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes": {
-      "description": "Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Natural sort? No (positive values only) * Self-delimiting? Yes * Compatibility? - BigQuery Federation `BINARY` encoding - HBase `Bytes.toBytes` - Java `ByteBuffer.putLong()` with `ByteOrder.BIG_ENDIAN`",
+      "description": "Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Order-preserving? No (positive values only) * Self-delimiting? Yes * Compatibility? - BigQuery Federation `BINARY` encoding - HBase `Bytes.toBytes` - Java `ByteBuffer.putLong()` with `ByteOrder.BIG_ENDIAN`",
       "id": "GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes",
       "properties": {
         "bytesType": {
           "$ref": "GoogleBigtableAdminV2TypeBytes",
-          "description": "The underlying `Bytes` type, which may be able to encode further."
+          "description": "Deprecated: ignored if set."
         }
       },
       "type": "object"
@@ -4103,7 +4103,7 @@
       "type": "object"
     },
     "Type": {
-      "description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. This might involve composing a series of steps into an \"encoding chain,\" for example to convert from INT64 -\u003e STRING -\u003e raw bytes. In most cases, a \"link\" in the encoding chain will be based an on existing GoogleSQL conversion function like `CAST`. Each link in the encoding chain also defines the following properties: * Natural sort: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING does *not* preserve sort order when dealing with negative numbers. INT64(1) \u003e INT64(-1), but STRING(\"-00001\") \u003e STRING(\"00001). - The overall encoding chain has this property if *every* link does. * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. - The overall encoding chain has this property if *any* link does. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
+      "description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. Each encoding also defines the following properties: * Order-preserving: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 as a fixed-width decimal string does *not* preserve sort order when dealing with negative numbers. INT64(1) \u003e INT64(-1), but STRING(\"-00001\") \u003e STRING(\"00001). * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
       "id": "Type",
       "properties": {
         "aggregateType": {

bigtableadmin/v2/bigtableadmin-gen.go

@@ -2540,7 +2540,7 @@
       }
     }
   },
-  "revision": "20240618",
+  "revision": "20240619",
   "rootUrl": "https://container.googleapis.com/",
   "schemas": {
     "AcceleratorConfig": {
@@ -2676,6 +2676,10 @@
           "$ref": "NetworkPolicyConfig",
           "description": "Configuration for NetworkPolicy. This only tracks whether the addon is enabled or not on the Master, it does not track whether network policy is enabled for the nodes."
         },
+        "rayOperatorConfig": {
+          "$ref": "RayOperatorConfig",
+          "description": "Optional. Configuration for Ray Operator addon."
+        },
         "statefulHaConfig": {
           "$ref": "StatefulHAConfig",
           "description": "Optional. Configuration for the StatefulHA add-on."
@@ -6272,6 +6276,47 @@
       },
       "type": "object"
     },
+    "RayClusterLoggingConfig": {
+      "description": "RayClusterLoggingConfig specifies configuration of Ray logging.",
+      "id": "RayClusterLoggingConfig",
+      "properties": {
+        "enabled": {
+          "description": "Enable log collection for Ray clusters.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "RayClusterMonitoringConfig": {
+      "description": "RayClusterMonitoringConfig specifies monitoring configuration for Ray clusters.",
+      "id": "RayClusterMonitoringConfig",
+      "properties": {
+        "enabled": {
+          "description": "Enable metrics collection for Ray clusters.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "RayOperatorConfig": {
+      "description": "Configuration options for the Ray Operator add-on.",
+      "id": "RayOperatorConfig",
+      "properties": {
+        "enabled": {
+          "description": "Whether the Ray Operator addon is enabled for this cluster.",
+          "type": "boolean"
+        },
+        "rayClusterLoggingConfig": {
+          "$ref": "RayClusterLoggingConfig",
+          "description": "Optional. Logging configuration for Ray clusters."
+        },
+        "rayClusterMonitoringConfig": {
+          "$ref": "RayClusterMonitoringConfig",
+          "description": "Optional. Monitoring configuration for Ray clusters."
+        }
+      },
+      "type": "object"
+    },
     "RecurringTimeWindow": {
       "description": "Represents an arbitrary window of time that recurs.",
       "id": "RecurringTimeWindow",

container/v1/container-api.json

@@ -2236,7 +2236,7 @@
       }
     }
   },
-  "revision": "20240608",
+  "revision": "20240629",
   "rootUrl": "https://dataform.googleapis.com/",
   "schemas": {
     "Assertion": {
@@ -2543,6 +2543,12 @@
           "readOnly": true,
           "type": "array"
         },
+        "createTime": {
+          "description": "Output only. The timestamp of when the compilation result was created.",
+          "format": "google-datetime",
+          "readOnly": true,
+          "type": "string"
+        },
         "dataEncryptionState": {
           "$ref": "DataEncryptionState",
           "description": "Output only. Only set if the repository has a KMS Key.",
@@ -3983,6 +3989,12 @@
       "description": "Represents a Dataform workflow configuration.",
       "id": "WorkflowConfig",
       "properties": {
+        "createTime": {
+          "description": "Output only. The timestamp of when the WorkflowConfig was created.",
+          "format": "google-datetime",
+          "readOnly": true,
+          "type": "string"
+        },
         "cronSchedule": {
           "description": "Optional. Optional schedule (in cron format) for automatic execution of this workflow config.",
           "type": "string"
@@ -4010,6 +4022,12 @@
         "timeZone": {
           "description": "Optional. Specifies the time zone to be used when interpreting cron_schedule. Must be a time zone name from the time zone database (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). If left unspecified, the default is UTC.",
           "type": "string"
+        },
+        "updateTime": {
+          "description": "Output only. The timestamp of when the WorkflowConfig was last updated.",
+          "format": "google-datetime",
+          "readOnly": true,
+          "type": "string"
         }
       },
       "type": "object"