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

googleapis · Feb 24, 2022 · 8a3061f · 8a3061f
1 parent 0954e33
commit 8a3061f
Show file tree

Hide file tree

Showing 43 changed files with 32,853 additions and 16,619 deletions.
diff --git a/alertcenter/v1beta1/alertcenter-api.json b/alertcenter/v1beta1/alertcenter-api.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"

diff --git a/alertcenter/v1beta1/alertcenter-gen.go b/alertcenter/v1beta1/alertcenter-gen.go
diff --git a/analyticsadmin/v1alpha/analyticsadmin-api.json b/analyticsadmin/v1alpha/analyticsadmin-api.json