feat(alertcenter): update the api

#### alertcenter:v1beta1

The following keys were added:
- schemas.GoogleOperations.properties.domain.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/alertcenter_v1beta1.alerts.html

@@ -242,7 +242,7 @@ <h3>Method Details</h3>
     &quot;alertId&quot;: &quot;A String&quot;, # Output only. The alert identifier.
     &quot;assignee&quot;: &quot;A String&quot;, # The email address of the user assigned to the alert.
     &quot;customerId&quot;: &quot;A String&quot;, # Output only. The unique identifier of the Google account of the customer.
-    &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
+    &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
     &quot;severity&quot;: &quot;A String&quot;, # The severity value of the alert. Alert Center will set this field at alert creation time, default&#x27;s to an empty string when it could not be determined. The supported values for update actions on this field are the following: * HIGH * MEDIUM * LOW
     &quot;status&quot;: &quot;A String&quot;, # The current status of the alert. The supported values are the following: * NOT_STARTED * IN_PROGRESS * CLOSED
     &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this metadata was last updated.
@@ -274,7 +274,7 @@ <h3>Method Details</h3>
   &quot;alertId&quot;: &quot;A String&quot;, # Output only. The alert identifier.
   &quot;assignee&quot;: &quot;A String&quot;, # The email address of the user assigned to the alert.
   &quot;customerId&quot;: &quot;A String&quot;, # Output only. The unique identifier of the Google account of the customer.
-  &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
+  &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
   &quot;severity&quot;: &quot;A String&quot;, # The severity value of the alert. Alert Center will set this field at alert creation time, default&#x27;s to an empty string when it could not be determined. The supported values for update actions on this field are the following: * HIGH * MEDIUM * LOW
   &quot;status&quot;: &quot;A String&quot;, # The current status of the alert. The supported values are the following: * NOT_STARTED * IN_PROGRESS * CLOSED
   &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this metadata was last updated.
@@ -315,7 +315,7 @@ <h3>Method Details</h3>
         &quot;alertId&quot;: &quot;A String&quot;, # Output only. The alert identifier.
         &quot;assignee&quot;: &quot;A String&quot;, # The email address of the user assigned to the alert.
         &quot;customerId&quot;: &quot;A String&quot;, # Output only. The unique identifier of the Google account of the customer.
-        &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
+        &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
         &quot;severity&quot;: &quot;A String&quot;, # The severity value of the alert. Alert Center will set this field at alert creation time, default&#x27;s to an empty string when it could not be determined. The supported values for update actions on this field are the following: * HIGH * MEDIUM * LOW
         &quot;status&quot;: &quot;A String&quot;, # The current status of the alert. The supported values are the following: * NOT_STARTED * IN_PROGRESS * CLOSED
         &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this metadata was last updated.
@@ -380,7 +380,7 @@ <h3>Method Details</h3>
     &quot;alertId&quot;: &quot;A String&quot;, # Output only. The alert identifier.
     &quot;assignee&quot;: &quot;A String&quot;, # The email address of the user assigned to the alert.
     &quot;customerId&quot;: &quot;A String&quot;, # Output only. The unique identifier of the Google account of the customer.
-    &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
+    &quot;etag&quot;: &quot;A String&quot;, # Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.
     &quot;severity&quot;: &quot;A String&quot;, # The severity value of the alert. Alert Center will set this field at alert creation time, default&#x27;s to an empty string when it could not be determined. The supported values for update actions on this field are the following: * HIGH * MEDIUM * LOW
     &quot;status&quot;: &quot;A String&quot;, # The current status of the alert. The supported values are the following: * NOT_STARTED * IN_PROGRESS * CLOSED
     &quot;updateTime&quot;: &quot;A String&quot;, # Output only. The time this metadata was last updated.

googleapiclient/discovery_cache/documents/alertcenter.v1beta1.json

@@ -423,7 +423,7 @@
       }
     }
   },
-  "revision": "20220131",
+  "revision": "20220221",
   "rootUrl": "https://alertcenter.googleapis.com/",
   "schemas": {
     "AccountSuspensionDetails": {
@@ -713,7 +713,7 @@
           "type": "string"
         },
         "etag": {
-          "description": "Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metatdata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.",
+          "description": "Optional. `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of an alert metadata from overwriting each other. It is strongly suggested that systems make use of the `etag` in the read-modify-write cycle to perform metadata updates in order to avoid race conditions: An `etag` is returned in the response which contains alert metadata, and systems are expected to put that etag in the request to update alert metadata to ensure that their change will be applied to the same version of the alert metadata. If no `etag` is provided in the call to update alert metadata, then the existing alert metadata is overwritten blindly.",
           "type": "string"
         },
         "severity": {
@@ -1153,6 +1153,10 @@
           "description": "A detailed, freeform incident description.",
           "type": "string"
         },
+        "domain": {
+          "description": "Customer domain for email template personalization.",
+          "type": "string"
+        },
         "header": {
           "description": "A header to display above the incident message. Typically used to attach a localized notice on the timeline for followup comms translations.",
           "type": "string"