MNTS-90534 : Clarify behavior of renotify_statuses when not explicitly set (#1574)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-04-04 17:56:36.285390",
-            "spec_repo_commit": "bf950df2"
+            "regenerated": "2024-04-04 19:22:22.387463",
+            "spec_repo_commit": "fd06108d"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-04-04 17:56:36.306538",
-            "spec_repo_commit": "bf950df2"
+            "regenerated": "2024-04-04 19:22:22.408419",
+            "spec_repo_commit": "fd06108d"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -7067,8 +7067,13 @@ components:
           nullable: true
           type: integer
         renotify_statuses:
-          description: The types of monitor statuses for which re-notification messages
+          description: 'The types of monitor statuses for which re-notification messages
             are sent.
+
+            Default: **null** if `renotify_interval` is **null**.
+
+            If `renotify_interval` is set, defaults to renotify on `Alert` and `No
+            Data`.'
           items:
             $ref: '#/components/schemas/MonitorRenotifyStatusType'
           nullable: true

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

@@ -143,6 +143,8 @@ export class MonitorOptions {
   "renotifyOccurrences"?: number;
   /**
    * The types of monitor statuses for which re-notification messages are sent.
+   * Default: **null** if `renotify_interval` is **null**.
+   * If `renotify_interval` is set, defaults to renotify on `Alert` and `No Data`.
    */
   "renotifyStatuses"?: Array<MonitorRenotifyStatusType>;
   /**