feat(all): auto-regenerate discovery clients

contactcenteraiplatform/v1alpha1/contactcenteraiplatform-api.json

@@ -512,7 +512,7 @@
       }
     }
   },
-  "revision": "20240416",
+  "revision": "20240419",
   "rootUrl": "https://contactcenteraiplatform.googleapis.com/",
   "schemas": {
     "AdminUser": {
@@ -562,6 +562,10 @@
           "description": "Required. A user friendly name for the ContactCenter.",
           "type": "string"
         },
+        "early": {
+          "$ref": "Early",
+          "description": "Optional. Early release channel."
+        },
         "instanceConfig": {
           "$ref": "InstanceConfig",
           "description": "The configuration of this instance, it is currently immutable once created."
@@ -581,6 +585,10 @@
           "description": "name of resource",
           "type": "string"
         },
+        "normal": {
+          "$ref": "Normal",
+          "description": "Optional. Normal release channel."
+        },
         "privateComponents": {
           "description": "Output only. A list of UJET components that should be privately accessed. This field is set by reading settings from the data plane. For more information about the format of the component please refer to go/ccaip-vpc-sc-org-policy. This field is must be fully populated only for Create/Update resource operations. The main use case for this field is OrgPolicy checks via CPE.",
           "items": {
@@ -662,6 +670,12 @@
       },
       "type": "object"
     },
+    "Early": {
+      "description": "First Channel to receive the updates. Meant to dev/test instances",
+      "id": "Early",
+      "properties": {},
+      "type": "object"
+    },
     "Empty": {
       "description": "A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }",
       "id": "Empty",
@@ -838,6 +852,12 @@
       },
       "type": "object"
     },
+    "Normal": {
+      "description": "Instances in this Channel will receive updates after all instances in `Early` were updated + 2 days.",
+      "id": "Normal",
+      "properties": {},
+      "type": "object"
+    },
     "Operation": {
       "description": "This resource represents a long-running operation that is the result of a network API call.",
       "id": "Operation",

monitoring/v3/monitoring-api.json

@@ -2714,7 +2714,7 @@
       }
     }
   },
-  "revision": "20240303",
+  "revision": "20240414",
   "rootUrl": "https://monitoring.googleapis.com/",
   "schemas": {
     "Aggregation": {
@@ -3453,7 +3453,7 @@
       "type": "object"
     },
     "Documentation": {
-      "description": "A content string and a MIME type that describes the content string's format.",
+      "description": "Documentation that is included in the notifications and incidents pertaining to this policy.",
       "id": "Documentation",
       "properties": {
         "content": {
@@ -3859,7 +3859,7 @@
         },
         "authInfo": {
           "$ref": "BasicAuthentication",
-          "description": "The authentication information. Optional when creating an HTTP check; defaults to empty."
+          "description": "The authentication information. Optional when creating an HTTP check; defaults to empty. Do not set both auth_method and auth_info."
         },
         "body": {
           "description": "The request body associated with the HTTP POST request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the request_method is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte.Note: If client libraries aren't used (which performs the conversion automatically) base64 encode your body data since the field is of bytes type.",
@@ -3922,6 +3922,10 @@
           ],
           "type": "string"
         },
+        "serviceAgentAuthentication": {
+          "$ref": "ServiceAgentAuthentication",
+          "description": "If specified, Uptime will generate and attach an OIDC JWT token for the Monitoring service agent service account as an Authorization header in the HTTP request when probing."
+        },
         "useSsl": {
           "description": "If true, use HTTPS instead of HTTP to run the check.",
           "type": "boolean"
@@ -5384,6 +5388,25 @@
       },
       "type": "object"
     },
+    "ServiceAgentAuthentication": {
+      "description": "Contains information needed for generating an OpenID Connect token (https://developers.google.com/identity/protocols/OpenIDConnect). The OIDC token will be generated for the Monitoring service agent service account.",
+      "id": "ServiceAgentAuthentication",
+      "properties": {
+        "type": {
+          "description": "Type of authentication.",
+          "enum": [
+            "SERVICE_AGENT_AUTHENTICATION_TYPE_UNSPECIFIED",
+            "OIDC_TOKEN"
+          ],
+          "enumDescriptions": [
+            "Default value, will result in OIDC Authentication.",
+            "OIDC Authentication"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "ServiceLevelIndicator": {
       "description": "A Service-Level Indicator (SLI) describes the \"performance\" of a service. For some services, the SLI is well-defined. In such cases, the SLI can be described easily by referencing the well-known SLI and providing the needed parameters. Alternatively, a \"custom\" SLI can be defined with a query to the underlying metric store. An SLI is defined to be good_service / total_service over any queried time interval. The value of performance always falls into the range 0 \u003c= performance \u003c= 1. A custom SLI describes how to compute this ratio, whether this is by dividing values from a pair of time series, cutting a Distribution into good and bad counts, or counting time windows in which the service complies with a criterion. For separation of concerns, a single Service-Level Indicator measures performance for only one aspect of service quality, such as fraction of successful queries or fast-enough queries.",
       "id": "ServiceLevelIndicator",