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

Author: yoshi-automation

accesscontextmanager/v1/accesscontextmanager-api.json

@@ -12,7 +12,7 @@
   "baseUrl": "https://accesscontextmanager.googleapis.com/",
   "batchPath": "batch",
   "canonicalName": "Access Context Manager",
-  "description": "An API for setting attribute based access control to requests to Google Cloud services.",
+  "description": "An API for setting attribute based access control to requests to Google Cloud services. *Warning:* Do not mix *v1alpha* and *v1* API usage in the same access policy. The v1alpha API supports new Access Context Manager features, which may have different attributes or behaviors that are not supported by v1. The practice of mixed API usage within a policy may result in the inability to update that policy, including any access levels or service perimeters belonging to it. It is not recommended to use both v1 and v1alpha for modifying policies with critical service perimeters. Modifications using v1alpha should be limited to policies with non-production/non-critical service perimeters.",
   "discoveryVersion": "v1",
   "documentationLink": "https://cloud.google.com/access-context-manager/docs/reference/rest/",
   "fullyEncodeReservedExpansion": true,
@@ -1290,7 +1290,7 @@
       }
     }
   },
-  "revision": "20240126",
+  "revision": "20240221",
   "rootUrl": "https://accesscontextmanager.googleapis.com/",
   "schemas": {
     "AccessContextManagerOperationMetadata": {

alloydb/v1/alloydb-api.json

@@ -4726,7 +4726,7 @@
       }
     }
   },
-  "revision": "20240219",
+  "revision": "20240222",
   "rootUrl": "https://androidpublisher.googleapis.com/",
   "schemas": {
     "Abi": {
@@ -5133,13 +5133,17 @@
             "RECOVERY_STATUS_UNSPECIFIED",
             "RECOVERY_STATUS_ACTIVE",
             "RECOVERY_STATUS_CANCELED",
-            "RECOVERY_STATUS_DRAFT"
+            "RECOVERY_STATUS_DRAFT",
+            "RECOVERY_STATUS_GENERATION_IN_PROGRESS",
+            "RECOVERY_STATUS_GENERATION_FAILED"
           ],
           "enumDescriptions": [
             "RecoveryStatus is unspecified.",
             "The app recovery action has not been canceled since it has been created.",
             "The recovery action has been canceled. The action cannot be resumed.",
-            "The recovery action is in the draft state and has not yet been deployed to users."
+            "The recovery action is in the draft state and has not yet been deployed to users.",
+            "The recovery action is generating recovery apks.",
+            "The app recovery action generation has failed."
           ],
           "type": "string"
         },
@@ -5151,7 +5155,7 @@
       "type": "object"
     },
     "AppVersionList": {
-      "description": "Data format for a list of app versions. Only one app version is supported for now.",
+      "description": "Data format for a list of app versions.",
       "id": "AppVersionList",
       "properties": {
         "versionCodes": {
@@ -6526,13 +6530,17 @@
             "RECOVERY_STATUS_UNSPECIFIED",
             "RECOVERY_STATUS_ACTIVE",
             "RECOVERY_STATUS_CANCELED",
-            "RECOVERY_STATUS_DRAFT"
+            "RECOVERY_STATUS_DRAFT",
+            "RECOVERY_STATUS_GENERATION_IN_PROGRESS",
+            "RECOVERY_STATUS_GENERATION_FAILED"
           ],
           "enumDescriptions": [
             "RecoveryStatus is unspecified.",
             "The app recovery action has not been canceled since it has been created.",
             "The recovery action has been canceled. The action cannot be resumed.",
-            "The recovery action is in the draft state and has not yet been deployed to users."
+            "The recovery action is in the draft state and has not yet been deployed to users.",
+            "The recovery action is generating recovery apks.",
+            "The app recovery action generation has failed."
           ],
           "type": "string"
         }

alloydb/v1/alloydb-gen.go

@@ -1102,7 +1102,7 @@
       "name": "chat",
       "version": "v1",
       "title": "Google Chat API",
-      "description": "Enables apps to fetch information and perform actions in Google Chat. Authentication is a prerequisite for using the Google Chat REST API.",
+      "description": "The Google Chat API lets you build Chat apps to integrate your services with Google Chat and manage Chat resources such as spaces, members, and messages.",
       "discoveryRestUrl": "https://chat.googleapis.com/$discovery/rest?version=v1",
       "icons": {
         "x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",

alloydb/v1alpha/alloydb-api.json

@@ -1651,7 +1651,7 @@
       }
     }
   },
-  "revision": "20240212",
+  "revision": "20240218",
   "rootUrl": "https://appengine.googleapis.com/",
   "schemas": {
     "ApiConfigHandler": {
@@ -2060,13 +2060,11 @@
       "id": "ContainerState",
       "properties": {
         "currentReasons": {
-          "$ref": "Reasons",
-          "deprecated": true
+          "$ref": "Reasons"
         },
         "previousReasons": {
           "$ref": "Reasons",
-          "deprecated": true,
-          "description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state.Reasons fields are deprecated. New tenants should only use the state field. If you must know the reason(s) behind a specific state, please consult with CCFE team first ([email protected])."
+          "description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state."
         },
         "state": {
           "description": "The current state of the container. This state is the culmination of all of the opinions from external systems that CCFE knows about of the container.",
@@ -3524,6 +3522,10 @@
           "$ref": "Date",
           "description": "Date when Runtime is deprecated."
         },
+        "displayName": {
+          "description": "User-friendly display name, e.g. 'Node.js 12', etc.",
+          "type": "string"
+        },
         "endOfSupportDate": {
           "$ref": "Date",
           "description": "Date when Runtime is end of support."