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

Author: yoshi-automation

chat/v1/chat-api.json

@@ -957,7 +957,7 @@
       }
     }
   },
-  "revision": "20231114",
+  "revision": "20231121",
   "rootUrl": "https://chat.googleapis.com/",
   "schemas": {
     "ActionParameter": {
@@ -981,7 +981,7 @@
       "properties": {
         "dialogAction": {
           "$ref": "DialogAction",
-          "description": "Input only. A response to an event related to a [dialog](https://developers.google.com/chat/how-tos/dialogs). Must be accompanied by `ResponseType.Dialog`."
+          "description": "Input only. A response to an interaction event related to a [dialog](https://developers.google.com/chat/how-tos/dialogs). Must be accompanied by `ResponseType.Dialog`."
         },
         "type": {
           "description": "Input only. The type of Chat app response.",
@@ -991,18 +991,24 @@
             "UPDATE_MESSAGE",
             "UPDATE_USER_MESSAGE_CARDS",
             "REQUEST_CONFIG",
-            "DIALOG"
+            "DIALOG",
+            "UPDATE_WIDGET"
           ],
           "enumDescriptions": [
             "Default type that's handled as `NEW_MESSAGE`.",
             "Post as a new message in the topic.",
             "Update the Chat app's message. This is only permitted on a `CARD_CLICKED` event where the message sender type is `BOT`.",
             "Update the cards on a user's message. This is only permitted as a response to a `MESSAGE` event with a matched url, or a `CARD_CLICKED` event where the message sender type is `HUMAN`. Text is ignored.",
             "Privately ask the user for additional authentication or configuration.",
-            "Presents a [dialog](https://developers.google.com/chat/how-tos/dialogs)."
+            "Presents a [dialog](https://developers.google.com/chat/how-tos/dialogs).",
+            "Widget text autocomplete options query."
           ],
           "type": "string"
         },
+        "updatedWidget": {
+          "$ref": "UpdatedWidget",
+          "description": "Input only. The response of the updated widget."
+        },
         "url": {
           "description": "Input only. URL for users to authenticate or configure. (Only for `REQUEST_CONFIG` response types.)",
           "type": "string"
@@ -1561,14 +1567,16 @@
             "MESSAGE",
             "ADDED_TO_SPACE",
             "REMOVED_FROM_SPACE",
-            "CARD_CLICKED"
+            "CARD_CLICKED",
+            "WIDGET_UPDATED"
           ],
           "enumDescriptions": [
             "Default value for the enum. DO NOT USE.",
             "A user sends the Chat app a message, or invokes the Chat app in a space.",
             "A user adds the Chat app to a space, or a Google Workspace administrator installs the Chat app in direct message spaces for users in their organization.",
             "A user removes the Chat app from a space.",
-            "A user clicks an interactive element of a card or dialog from a Chat app, such as a button. If a user interacts with a dialog, the `CARD_CLICKED` interaction event's `isDialogEvent` field is set to `true` and includes a [`DialogEventType`](https://developers.google.com/chat/api/reference/rest/v1/DialogEventType)."
+            "A user clicks an interactive element of a card or dialog from a Chat app, such as a button. If a user interacts with a dialog, the `CARD_CLICKED` interaction event's `isDialogEvent` field is set to `true` and includes a [`DialogEventType`](https://developers.google.com/chat/api/reference/rest/v1/DialogEventType).",
+            "A user updates a widget in a card message or dialog."
           ],
           "type": "string"
         },
@@ -3310,6 +3318,20 @@
       },
       "type": "object"
     },
+    "SelectionItems": {
+      "description": "List of widget autocomplete results.",
+      "id": "SelectionItems",
+      "properties": {
+        "items": {
+          "description": "An array of the SelectionItem objects.",
+          "items": {
+            "$ref": "GoogleAppsCardV1SelectionItem"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
     "SetUpSpaceRequest": {
       "id": "SetUpSpaceRequest",
       "properties": {
@@ -3622,6 +3644,21 @@
       },
       "type": "object"
     },
+    "UpdatedWidget": {
+      "description": "The response of the updated widget. Used to provide autocomplete options for a widget.",
+      "id": "UpdatedWidget",
+      "properties": {
+        "suggestions": {
+          "$ref": "SelectionItems",
+          "description": "List of widget autocomplete results"
+        },
+        "widget": {
+          "description": "The ID of the updated widget. The ID must match the one for the widget that triggered the update request.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "UploadAttachmentRequest": {
       "id": "UploadAttachmentRequest",
       "properties": {

chat/v1/chat-gen.go

@@ -557,7 +557,7 @@
       }
     }
   },
-  "revision": "20231011",
+  "revision": "20231127",
   "rootUrl": "https://chromepolicy.googleapis.com/",
   "schemas": {
     "GoogleChromePolicyVersionsV1AdditionalTargetKeyName": {
@@ -1628,7 +1628,7 @@
           "type": "integer"
         },
         "proto3Optional": {
-          "description": "If true, this is a proto3 \"optional\". When a proto3 field is optional, it tracks presence regardless of field type. When proto3_optional is true, this field must be belong to a oneof to signal to old proto3 clients that presence is tracked for this field. This oneof is known as a \"synthetic\" oneof, and this field must be its sole member (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs exist in the descriptor only, and do not generate any API. Synthetic oneofs must be ordered after all \"real\" oneofs. For message fields, proto3_optional doesn't create any semantic change, since non-repeated message fields always track presence. However it still indicates the semantic detail of whether the user wrote \"optional\" or not. This can be useful for round-tripping the .proto file. For consistency we give message fields a synthetic oneof also, even though it is not required to track presence. This is especially important because the parser can't tell if a field is a message or an enum, so it must always create a synthetic oneof. Proto2 optional fields do not set this flag, because they already indicate optional with `LABEL_OPTIONAL`.",
+          "description": "If true, this is a proto3 \"optional\". When a proto3 field is optional, it tracks presence regardless of field type. When proto3_optional is true, this field must belong to a oneof to signal to old proto3 clients that presence is tracked for this field. This oneof is known as a \"synthetic\" oneof, and this field must be its sole member (each proto3 optional field gets its own synthetic oneof). Synthetic oneofs exist in the descriptor only, and do not generate any API. Synthetic oneofs must be ordered after all \"real\" oneofs. For message fields, proto3_optional doesn't create any semantic change, since non-repeated message fields always track presence. However it still indicates the semantic detail of whether the user wrote \"optional\" or not. This can be useful for round-tripping the .proto file. For consistency we give message fields a synthetic oneof also, even though it is not required to track presence. This is especially important because the parser can't tell if a field is a message or an enum, so it must always create a synthetic oneof. Proto2 optional fields do not set this flag, because they already indicate optional with `LABEL_OPTIONAL`.",
           "type": "boolean"
         },
         "type": {

chromepolicy/v1/chromepolicy-api.json

@@ -1985,7 +1985,7 @@
                   ],
                   "parameters": {
                     "firewallEndpointAssociationId": {
-                      "description": "Required. Id of the requesting object. If auto-generating Id server-side, remove this field and firewall_endpoint_association_id from the method_signature of Create RPC.",
+                      "description": "Optional. Id of the requesting object. If auto-generating Id server-side, remove this field and firewall_endpoint_association_id from the method_signature of Create RPC.",
                       "location": "query",
                       "type": "string"
                     },
@@ -3162,7 +3162,7 @@
       }
     }
   },
-  "revision": "20230920",
+  "revision": "20231101",
   "rootUrl": "https://networksecurity.googleapis.com/",
   "schemas": {
     "AddAddressGroupItemsRequest": {