Regenerate client from commit e327e6df of spec repo (#2662)

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

Author: 3 people

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-02 16:34:57.377290",
-            "spec_repo_commit": "de2517ad"
+            "regenerated": "2025-07-02 20:43:17.503949",
+            "spec_repo_commit": "e327e6df"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-02 16:34:57.570480",
-            "spec_repo_commit": "de2517ad"
+            "regenerated": "2025-07-02 20:43:17.520727",
+            "spec_repo_commit": "e327e6df"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -53140,9 +53140,6 @@ paths:
         operator: OR
         permissions:
         - monitors_read
-      x-unstable: '**Note**: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).'
     post:
       description: Creates a monitor notification rule.
       operationId: CreateMonitorNotificationRule
@@ -53186,9 +53183,6 @@ paths:
         operator: OR
         permissions:
         - monitor_config_policy_write
-      x-unstable: '**Note**: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/monitor/notification_rule/{rule_id}:
     delete:
       description: Deletes a monitor notification rule by `rule_id`.
@@ -53229,9 +53223,6 @@ paths:
         operator: OR
         permissions:
         - monitor_config_policy_write
-      x-unstable: '**Note**: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).'
     get:
       description: Returns a monitor notification rule by `rule_id`.
       operationId: GetMonitorNotificationRule
@@ -53285,9 +53276,6 @@ paths:
         operator: OR
         permissions:
         - monitors_read
-      x-unstable: '**Note**: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).'
     patch:
       description: Updates a monitor notification rule by `rule_id`.
       operationId: UpdateMonitorNotificationRule
@@ -53345,9 +53333,6 @@ paths:
         operator: OR
         permissions:
         - monitor_config_policy_write
-      x-unstable: '**Note**: This endpoint is in Preview. If you have any feedback,
-
-        contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/monitor/policy:
     get:
       description: Get all monitor configuration policies.

examples/v2/monitors/CreateMonitorNotificationRule.py

@@ -31,7 +31,6 @@
 )
 
 configuration = Configuration()
-configuration.unstable_operations["create_monitor_notification_rule"] = True
 with ApiClient(configuration) as api_client:
     api_instance = MonitorsApi(api_client)
     response = api_instance.create_monitor_notification_rule(body=body)

examples/v2/monitors/DeleteMonitorNotificationRule.py

@@ -10,7 +10,6 @@
 MONITOR_NOTIFICATION_RULE_DATA_ID = environ["MONITOR_NOTIFICATION_RULE_DATA_ID"]
 
 configuration = Configuration()
-configuration.unstable_operations["delete_monitor_notification_rule"] = True
 with ApiClient(configuration) as api_client:
     api_instance = MonitorsApi(api_client)
     api_instance.delete_monitor_notification_rule(

examples/v2/monitors/GetMonitorNotificationRule.py

@@ -10,7 +10,6 @@
 MONITOR_NOTIFICATION_RULE_DATA_ID = environ["MONITOR_NOTIFICATION_RULE_DATA_ID"]
 
 configuration = Configuration()
-configuration.unstable_operations["get_monitor_notification_rule"] = True
 with ApiClient(configuration) as api_client:
     api_instance = MonitorsApi(api_client)
     response = api_instance.get_monitor_notification_rule(

examples/v2/monitors/GetMonitorNotificationRules.py

@@ -6,7 +6,6 @@
 from datadog_api_client.v2.api.monitors_api import MonitorsApi
 
 configuration = Configuration()
-configuration.unstable_operations["get_monitor_notification_rules"] = True
 with ApiClient(configuration) as api_client:
     api_instance = MonitorsApi(api_client)
     response = api_instance.get_monitor_notification_rules()

examples/v2/monitors/UpdateMonitorNotificationRule.py

@@ -36,7 +36,6 @@
 )
 
 configuration = Configuration()
-configuration.unstable_operations["update_monitor_notification_rule"] = True
 with ApiClient(configuration) as api_client:
     api_instance = MonitorsApi(api_client)
     response = api_instance.update_monitor_notification_rule(rule_id=MONITOR_NOTIFICATION_RULE_DATA_ID, body=body)

src/datadog_api_client/configuration.py

@@ -288,15 +288,10 @@ def __init__(
                 "v2.list_aws_namespaces": False,
                 "v2.update_aws_account": False,
                 "v2.list_aws_logs_services": False,
-                "v2.create_monitor_notification_rule": False,
                 "v2.create_monitor_user_template": False,
-                "v2.delete_monitor_notification_rule": False,
                 "v2.delete_monitor_user_template": False,
-                "v2.get_monitor_notification_rule": False,
-                "v2.get_monitor_notification_rules": False,
                 "v2.get_monitor_user_template": False,
                 "v2.list_monitor_user_templates": False,
-                "v2.update_monitor_notification_rule": False,
                 "v2.update_monitor_user_template": False,
                 "v2.validate_existing_monitor_user_template": False,
                 "v2.validate_monitor_user_template": False,

tests/v2/features/monitors.feature

@@ -31,16 +31,14 @@ Feature: Monitors
 
   @skip-validation @team:DataDog/monitor-app
   Scenario: Create a monitor notification rule returns "Bad Request" response
-    Given operation "CreateMonitorNotificationRule" enabled
-    And new "CreateMonitorNotificationRule" request
+    Given new "CreateMonitorNotificationRule" request
     And body with value {"data": {"attributes": {"filter": {"tags": ["test:{{ unique_lower }}", "host:abc"]}, "name": "test rule", "recipients": ["@slack-test-channel", "@jira-test"]}, "type": "monitor-notification-rule"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/monitor-app
   Scenario: Create a monitor notification rule returns "OK" response
-    Given operation "CreateMonitorNotificationRule" enabled
-    And new "CreateMonitorNotificationRule" request
+    Given new "CreateMonitorNotificationRule" request
     And body with value {"data": {"attributes": {"filter": {"tags": ["test:{{ unique_lower }}"]}, "name": "test rule", "recipients": ["slack-test-channel", "jira-test"]}, "type": "monitor-notification-rule"}}
     When the request is sent
     Then the response status is 200 OK
@@ -86,16 +84,14 @@ Feature: Monitors
 
   @team:DataDog/monitor-app
   Scenario: Delete a monitor notification rule returns "Not Found" response
-    Given operation "DeleteMonitorNotificationRule" enabled
-    And new "DeleteMonitorNotificationRule" request
+    Given new "DeleteMonitorNotificationRule" request
     And request contains "rule_id" parameter with value "00000000-0000-1234-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/monitor-app
   Scenario: Delete a monitor notification rule returns "OK" response
-    Given operation "DeleteMonitorNotificationRule" enabled
-    And there is a valid "monitor_notification_rule" in the system
+    Given there is a valid "monitor_notification_rule" in the system
     And new "DeleteMonitorNotificationRule" request
     And request contains "rule_id" parameter from "monitor_notification_rule.data.id"
     When the request is sent
@@ -170,16 +166,14 @@ Feature: Monitors
 
   @team:DataDog/monitor-app
   Scenario: Get a monitor notification rule returns "Not Found" response
-    Given operation "GetMonitorNotificationRule" enabled
-    And new "GetMonitorNotificationRule" request
+    Given new "GetMonitorNotificationRule" request
     And request contains "rule_id" parameter with value "00000000-0000-1234-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/monitor-app
   Scenario: Get a monitor notification rule returns "OK" response
-    Given operation "GetMonitorNotificationRule" enabled
-    And there is a valid "monitor_notification_rule" in the system
+    Given there is a valid "monitor_notification_rule" in the system
     And new "GetMonitorNotificationRule" request
     And request contains "rule_id" parameter from "monitor_notification_rule.data.id"
     When the request is sent
@@ -218,8 +212,7 @@ Feature: Monitors
 
   @team:DataDog/monitor-app
   Scenario: Get all monitor notification rules returns "OK" response
-    Given operation "GetMonitorNotificationRules" enabled
-    And there is a valid "monitor_notification_rule" in the system
+    Given there is a valid "monitor_notification_rule" in the system
     And new "GetMonitorNotificationRules" request
     When the request is sent
     Then the response status is 200 OK
@@ -237,8 +230,7 @@ Feature: Monitors
 
   @skip-validation @team:DataDog/monitor-app
   Scenario: Update a monitor notification rule returns "Bad Request" response
-    Given operation "UpdateMonitorNotificationRule" enabled
-    And there is a valid "monitor_notification_rule" in the system
+    Given there is a valid "monitor_notification_rule" in the system
     And new "UpdateMonitorNotificationRule" request
     And request contains "rule_id" parameter from "monitor_notification_rule.data.id"
     And body with value {"data": {"attributes": {"filter": {"tags": ["test:{{ unique_lower }}", "host:abc"]}, "name": "updated rule", "recipients": ["@slack-test-channel"]}, "id": "{{ monitor_notification_rule.data.id }}", "type": "monitor-notification-rule"}}
@@ -247,17 +239,15 @@ Feature: Monitors
 
   @team:DataDog/monitor-app
   Scenario: Update a monitor notification rule returns "Not Found" response
-    Given operation "UpdateMonitorNotificationRule" enabled
-    And new "UpdateMonitorNotificationRule" request
+    Given new "UpdateMonitorNotificationRule" request
     And request contains "rule_id" parameter with value "00000000-0000-1234-0000-000000000000"
     And body with value {"data": {"attributes": {"filter": {"tags": ["test:{{ unique_lower }}", "host:abc"]}, "name": "updated rule", "recipients": ["slack-test-channel", "jira-test"]}, "id": "00000000-0000-1234-0000-000000000000", "type": "monitor-notification-rule"}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/monitor-app
   Scenario: Update a monitor notification rule returns "OK" response
-    Given operation "UpdateMonitorNotificationRule" enabled
-    And there is a valid "monitor_notification_rule" in the system
+    Given there is a valid "monitor_notification_rule" in the system
     And new "UpdateMonitorNotificationRule" request
     And request contains "rule_id" parameter from "monitor_notification_rule.data.id"
     And body with value {"data": {"attributes": {"filter": {"tags": ["test:{{ unique_lower }}", "host:abc"]}, "name": "updated rule", "recipients": ["slack-test-channel"]}, "id": "{{ monitor_notification_rule.data.id }}", "type": "monitor-notification-rule"}}