feat(alertcenter): update the API

#### alertcenter:v1beta1 The following keys were added: - schemas.GoogleOperations.properties.domain.description - schemas.GoogleOperations.properties.domain.type The following keys were changed: - schemas.AlertMetadata.properties.etag.description - schemas.AppsOutage.properties.status.enum - schemas.AppsOutage.properties.status.enumDescriptions - schemas.MergeInfo.properties.newAlertId.description
googleapis · Mar 8, 2022 · 7904c52 · 7904c52
1 parent 844ef06
commit 7904c52
Show file tree

Hide file tree

Showing 2 changed files with 17 additions and 7 deletions.
diff --git a/discovery/alertcenter-v1beta1.json b/discovery/alertcenter-v1beta1.json
@@ -423,7 +423,7 @@
       }
     }
   },
-  "revision": "20211214",
+  "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": {
@@ -804,7 +804,8 @@
             "RESOLVED",
             "FALSE_POSITIVE",
             "PARTIALLY_RESOLVED",
-            "MERGED"
+            "MERGED",
+            "DOWNGRADED"
           ],
           "enumDescriptions": [
             "Status is unspecified.",
@@ -813,7 +814,8 @@
             "The incident has been resolved.",
             "Further assessment indicated no customer impact.",
             "The incident has been partially resolved.",
-            "The incident was merged into a parent."
+            "The incident was merged into a parent.",
+            "The incident has lower impact than initially anticipated."
           ],
           "type": "string"
         }
@@ -1151,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"
@@ -1289,7 +1295,7 @@
       "id": "MergeInfo",
       "properties": {
         "newAlertId": {
-          "description": "New alert ID. Reference the [google.apps.alertcenter.Alert] with this ID for the current state.",
+          "description": "Optional. New alert ID. Reference the [google.apps.alertcenter.Alert] with this ID for the current state.",
           "type": "string"
         },
         "newIncidentTrackingId": {

diff --git a/src/apis/alertcenter/v1beta1.ts b/src/apis/alertcenter/v1beta1.ts
@@ -330,7 +330,7 @@ export namespace alertcenter_v1beta1 {
      */
     customerId?: string | null;
     /**
-     * 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.
+     * 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.
      */
     etag?: string | null;
     /**
@@ -652,6 +652,10 @@ export namespace alertcenter_v1beta1 {
      * A detailed, freeform incident description.
      */
     description?: string | null;
+    /**
+     * Customer domain for email template personalization.
+     */
+    domain?: string | null;
     /**
      * A header to display above the incident message. Typically used to attach a localized notice on the timeline for followup comms translations.
      */
@@ -756,7 +760,7 @@ export namespace alertcenter_v1beta1 {
    */
   export interface Schema$MergeInfo {
     /**
-     * New alert ID. Reference the [google.apps.alertcenter.Alert] with this ID for the current state.
+     * Optional. New alert ID. Reference the [google.apps.alertcenter.Alert] with this ID for the current state.
      */
     newAlertId?: string | null;
     /**