Regenerate client from commit cd769d5 of spec repo (#133)

Co-authored-by: ci.datadog-api-spec <[email protected]>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.4.1.dev6",
-            "regenerated": "2021-05-17 13:51:56.851506",
-            "spec_repo_commit": "e34c19d"
+            "regenerated": "2021-05-18 08:19:41.200180",
+            "spec_repo_commit": "cd769d5"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev6",
-            "regenerated": "2021-05-17 13:52:02.727705",
-            "spec_repo_commit": "e34c19d"
+            "regenerated": "2021-05-18 08:19:46.080524",
+            "spec_repo_commit": "cd769d5"
         }
     }
 }

packages/datadog-api-client-v1/models/MonitorOptions.ts

@@ -30,7 +30,7 @@ export class MonitorOptions {
     */
     'enableLogsSample'?: boolean;
     /**
-    * A message to include with a re-notification. Supports the `@username` notification we allow elsewhere. Not applicable if `renotify_interval` is `None`.
+    * We recommend using the [is_renotify](https://docs.datadoghq.com/monitors/notifications/?tab=is_alert#renotify), block in the original message instead. A message to include with a re-notification. Supports the `@username` notification we allow elsewhere. Not applicable if `renotify_interval` is `None`.
     */
     'escalationMessage'?: string;
     /**