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

bigqueryreservation/v1/bigqueryreservation-api.json

@@ -935,7 +935,7 @@
       }
     }
   },
-  "revision": "20241110",
+  "revision": "20241209",
   "rootUrl": "https://bigqueryreservation.googleapis.com/",
   "schemas": {
     "Assignment": {
@@ -1346,15 +1346,17 @@
           "type": "string"
         },
         "originalPrimaryLocation": {
-          "description": "Optional. The original primary location of the reservation which is set only during its creation and remains unchanged afterwards. It can be used by the customer to answer questions about disaster recovery billing. The field is output only for customers and should not be specified, however, the `google.api.field_behavior` is not set to `OUTPUT_ONLY` since these fields are set in rerouted requests sent across regions.",
+          "description": "Output only. The location where the reservation was originally created. This is set only during the failover reservation's creation. All billing charges for the failover reservation will be applied to this location.",
+          "readOnly": true,
           "type": "string"
         },
         "primaryLocation": {
-          "description": "Optional. The primary location of the reservation. The field is only meaningful for a failover reservation that is used for managed disaster recovery. The field is output only for customers and should not be specified. However, the `google.api.field_behavior` is not set to `OUTPUT_ONLY` since these fields are set in rerouted requests sent across regions.",
+          "description": "Output only. The current location of the reservation's primary replica. This field is only set for reservations using the managed disaster recovery feature.",
+          "readOnly": true,
           "type": "string"
         },
         "secondaryLocation": {
-          "description": "Optional. The secondary location of the reservation that is used for managed disaster recovery. Customers can set this in create/update reservation calls to create a failover reservation or convert a non-failover reservation to a failover reservation.",
+          "description": "Optional. The current location of the reservation's secondary replica. This field is only set for reservations using the managed disaster recovery feature. Users can set this in create reservation calls to create a failover reservation or in update reservation calls to convert a non-failover reservation to a failover reservation(or vice versa).",
           "type": "string"
         },
         "slotCapacity": {

chat/v1/chat-api.json

@@ -48,22 +48,22 @@
           "description": "View members in Google Chat conversations."
         },
         "https://www.googleapis.com/auth/chat.messages": {
-          "description": "See, compose, send, update, and delete messages as well as their message content; add, see, and delete reactions to messages."
+          "description": "See, compose, send, update, and delete messages and their associated attachments, and add, see, and delete reactions to messages."
         },
         "https://www.googleapis.com/auth/chat.messages.create": {
           "description": "Compose and send messages in Google Chat"
         },
         "https://www.googleapis.com/auth/chat.messages.reactions": {
-          "description": "See, add, and delete reactions as well as their reaction content to messages in Google Chat"
+          "description": "See, add, and delete reactions to messages in Google Chat"
         },
         "https://www.googleapis.com/auth/chat.messages.reactions.create": {
           "description": "Add reactions to messages in Google Chat"
         },
         "https://www.googleapis.com/auth/chat.messages.reactions.readonly": {
-          "description": "View reactions as well as their reaction content to messages in Google Chat"
+          "description": "View reactions to messages in Google Chat"
         },
         "https://www.googleapis.com/auth/chat.messages.readonly": {
-          "description": "See messages as well as their reactions and message content in Google Chat"
+          "description": "See messages and their associated reactions and attachments in Google Chat"
         },
         "https://www.googleapis.com/auth/chat.spaces": {
           "description": "Create conversations and spaces and see or update metadata (including history settings and access settings) in Google Chat"
@@ -1344,7 +1344,7 @@
       }
     }
   },
-  "revision": "20241208",
+  "revision": "20241210",
   "rootUrl": "https://chat.googleapis.com/",
   "schemas": {
     "AccessSettings": {

config/v1/config-api.json

@@ -1187,7 +1187,7 @@
       }
     }
   },
-  "revision": "20241205",
+  "revision": "20241211",
   "rootUrl": "https://config.googleapis.com/",
   "schemas": {
     "ApplyResults": {
@@ -2556,7 +2556,7 @@
           "additionalProperties": {
             "$ref": "TerraformVariable"
           },
-          "description": "Input variable values for the Terraform blueprint.",
+          "description": "Optional. Input variable values for the Terraform blueprint.",
           "type": "object"
         }
       },
@@ -2568,7 +2568,8 @@
       "properties": {
         "error": {
           "$ref": "Status",
-          "description": "Original error response from underlying Google API, if available."
+          "description": "Output only. Original error response from underlying Google API, if available.",
+          "readOnly": true
         },
         "errorDescription": {
           "description": "A human-readable error description.",
@@ -2606,7 +2607,7 @@
       "id": "TerraformVariable",
       "properties": {
         "inputValue": {
-          "description": "Input variable value.",
+          "description": "Optional. Input variable value.",
           "type": "any"
         }
       },

domains/v1alpha2/domains-api.json

@@ -965,7 +965,7 @@
       }
     }
   },
-  "revision": "20240724",
+  "revision": "20241209",
   "rootUrl": "https://domains.googleapis.com/",
   "schemas": {
     "AuditConfig": {
@@ -1939,18 +1939,18 @@
       "type": "object"
     },
     "PostalAddress": {
-      "description": "Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478",
+      "description": "Represents a postal address. For example for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created by user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, see: https://support.google.com/business/answer/6397478",
       "id": "PostalAddress",
       "properties": {
         "addressLines": {
-          "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (e.g. \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (e.g. Japan), address_language is used to make it explicit (e.g. \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
+          "description": "Unstructured address lines describing the lower levels of an address. Because values in address_lines do not have type information and may sometimes contain multiple values in a single field (For example \"Austin, TX\"), it is important that the line order is clear. The order of address lines should be \"envelope order\" for the country/region of the address. In places where this can vary (For example Japan), address_language is used to make it explicit (For example \"ja\" for large-to-small ordering and \"ja-Latn\" or \"en\" for small-to-large). This way, the most specific line of an address can be selected based on the language. The minimum permitted structural representation of an address consists of a region_code with all remaining information placed in the address_lines. It would be possible to format such an address very approximately without geocoding, but no semantic reasoning could be made about any of the address components until it was at least partially resolved. Creating an address only containing a region_code and address_lines, and then geocoding is the recommended way to handle completely unstructured addresses (as opposed to guessing which parts of the address should be localities or administrative areas).",
           "items": {
             "type": "string"
           },
           "type": "array"
         },
         "administrativeArea": {
-          "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (e.g. \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. E.g. in Switzerland this should be left unpopulated.",
+          "description": "Optional. Highest administrative subdivision which is used for postal addresses of a country or region. For example, this can be a state, a province, an oblast, or a prefecture. Specifically, for Spain this is the province and not the autonomous community (For example \"Barcelona\" and not \"Catalonia\"). Many countries don't use an administrative area in postal addresses. For example in Switzerland this should be left unpopulated.",
           "type": "string"
         },
         "languageCode": {
@@ -1966,7 +1966,7 @@
           "type": "string"
         },
         "postalCode": {
-          "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (e.g. state/zip validation in the U.S.A.).",
+          "description": "Optional. Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address (For example state/zip validation in the U.S.A.).",
           "type": "string"
         },
         "recipients": {
@@ -1986,7 +1986,7 @@
           "type": "integer"
         },
         "sortingCode": {
-          "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (e.g. \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (e.g. Côte d'Ivoire).",
+          "description": "Optional. Additional, country-specific, sorting code. This is not used in most regions. Where it is used, the value is either a string like \"CEDEX\", optionally followed by a number (For example \"CEDEX 7\"), or just a number alone, representing the \"sector code\" (Jamaica), \"delivery area indicator\" (Malawi) or \"post office indicator\" (For example Côte d'Ivoire).",
           "type": "string"
         },
         "sublocality": {