Sync OpenAPI specification for (spec-v1-monitor.yaml)

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-03-17 17:20:28.246488",
-            "spec_repo_commit": "29344bf2"
+            "regenerated": "2025-03-18 00:14:01.428672",
+            "spec_repo_commit": "2738500d"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-03-17 17:20:28.261938",
-            "spec_repo_commit": "29344bf2"
+            "regenerated": "2025-03-18 00:14:01.452573",
+            "spec_repo_commit": "2738500d"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -29328,7 +29328,7 @@ paths:
       - description: 'When specified, shows additional information about the group
           states.
 
-          Choose one or more from `all`, `alert`, `warn`, and `no data` (`no%20data`).'
+          Choose one or more from `all`, `alert`, `warn`, and `no data`.'
         in: query
         name: group_states
         required: false
@@ -29913,15 +29913,15 @@ paths:
       - apiKeyAuth: []
         appKeyAuth: []
       - AuthZ:
-        - monitors_write
+        - monitors_read
       summary: Validate a monitor
       tags:
       - Monitors
       x-codegen-request-body-name: body
       x-permission:
         operator: OR
         permissions:
-        - monitors_write
+        - monitors_read
   /api/v1/monitor/{monitor_id}:
     delete:
       description: Delete the specified monitor
@@ -30214,15 +30214,15 @@ paths:
       - apiKeyAuth: []
         appKeyAuth: []
       - AuthZ:
-        - monitors_write
+        - monitors_read
       summary: Validate an existing monitor
       tags:
       - Monitors
       x-codegen-request-body-name: body
       x-permission:
         operator: OR
         permissions:
-        - monitors_write
+        - monitors_read
   /api/v1/monthly_custom_reports:
     get:
       deprecated: true
@@ -36863,7 +36863,10 @@ tags:
 
     scopes from alerting. Downtime settings, which can be scheduled with start and
 
-    end times, prevent all alerting related to specified Datadog tags.'
+    end times, prevent all alerting related to specified Datadog tags.
+
+
+    **Note:** `curl` commands require [url encoding](https://curl.se/docs/url-syntax.html).'
   name: Downtimes
 - description: 'The Event Management API allows you to programmatically post events
     to the Events Explorer and fetch events from the Events Explorer. See the [Event
@@ -36940,7 +36943,10 @@ tags:
     notifies your team when a defined threshold has exceeded.
 
 
-    For more information, see [Creating Monitors](https://docs.datadoghq.com/monitors/create/types/).'
+    For more information, see [Creating Monitors](https://docs.datadoghq.com/monitors/create/types/).
+
+
+    **Note:** `curl` commands require [url encoding](https://curl.se/docs/url-syntax.html).'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/monitors/create/types/

tests/scenarios/features/v1/downtimes.feature

@@ -4,7 +4,8 @@ Feature: Downtimes
   you greater control over monitor notifications by allowing you to globally
   exclude scopes from alerting. Downtime settings, which can be scheduled
   with start and end times, prevent all alerting related to specified
-  Datadog tags.
+  Datadog tags.  **Note:** `curl` commands require [url
+  encoding](https://curl.se/docs/url-syntax.html).
 
   Background:
     Given a valid "apiKeyAuth" key in the system

tests/scenarios/features/v1/monitors.feature

@@ -3,7 +3,9 @@ Feature: Monitors
   [Monitors](https://docs.datadoghq.com/monitors) allow you to watch a
   metric or check that you care about and notifies your team when a defined
   threshold has exceeded.  For more information, see [Creating
-  Monitors](https://docs.datadoghq.com/monitors/create/types/).
+  Monitors](https://docs.datadoghq.com/monitors/create/types/).  **Note:**
+  `curl` commands require [url encoding](https://curl.se/docs/url-
+  syntax.html).
 
   Background:
     Given a valid "apiKeyAuth" key in the system