Regenerate client from commit e327e6df of spec repo

ci.datadog-api-spec · ci.datadog-api-spec · commit d7a353ba04e4 · 2025-07-02T20:43:54.000Z
diff --git a/.apigentools-info b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-02 16:34:52.201607",
-            "spec_repo_commit": "de2517ad"
+            "regenerated": "2025-07-02 20:43:20.487037",
+            "spec_repo_commit": "e327e6df"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-02 16:34:52.217566",
-            "spec_repo_commit": "de2517ad"
+            "regenerated": "2025-07-02 20:43:20.503175",
+            "spec_repo_commit": "e327e6df"
         }
     }
 }
diff --git a/.generator/schemas/v2/openapi.yaml b/.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.
diff --git a/examples/v2/monitors/CreateMonitorNotificationRule.rb b/examples/v2/monitors/CreateMonitorNotificationRule.rb
@@ -1,9 +1,6 @@
 # Create a monitor notification rule returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.create_monitor_notification_rule".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::MonitorsAPI.new
 
 body = DatadogAPIClient::V2::MonitorNotificationRuleCreateRequest.new({
diff --git a/examples/v2/monitors/DeleteMonitorNotificationRule.rb b/examples/v2/monitors/DeleteMonitorNotificationRule.rb
@@ -1,9 +1,6 @@
 # Delete a monitor notification rule returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.delete_monitor_notification_rule".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::MonitorsAPI.new
 
 # there is a valid "monitor_notification_rule" in the system
diff --git a/examples/v2/monitors/GetMonitorNotificationRule.rb b/examples/v2/monitors/GetMonitorNotificationRule.rb
@@ -1,9 +1,6 @@
 # Get a monitor notification rule returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.get_monitor_notification_rule".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::MonitorsAPI.new
 
 # there is a valid "monitor_notification_rule" in the system
diff --git a/examples/v2/monitors/GetMonitorNotificationRules.rb b/examples/v2/monitors/GetMonitorNotificationRules.rb
@@ -1,8 +1,5 @@
 # Get all monitor notification rules returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.get_monitor_notification_rules".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::MonitorsAPI.new
 p api_instance.get_monitor_notification_rules()
diff --git a/examples/v2/monitors/UpdateMonitorNotificationRule.rb b/examples/v2/monitors/UpdateMonitorNotificationRule.rb
@@ -1,9 +1,6 @@
 # Update a monitor notification rule returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.update_monitor_notification_rule".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::MonitorsAPI.new
 
 # there is a valid "monitor_notification_rule" in the system
diff --git a/features/v2/monitors.feature b/features/v2/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"}}
diff --git a/lib/datadog_api_client/configuration.rb b/lib/datadog_api_client/configuration.rb
@@ -241,15 +241,10 @@ def initialize
             "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,
diff --git a/lib/datadog_api_client/v2/api/monitors_api.rb b/lib/datadog_api_client/v2/api/monitors_api.rb
@@ -106,12 +106,6 @@ def create_monitor_notification_rule(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(MonitorNotificationRuleResponse, Integer, Hash)>] MonitorNotificationRuleResponse data, response status code and response headers
     def create_monitor_notification_rule_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.create_monitor_notification_rule".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.create_monitor_notification_rule")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.create_monitor_notification_rule"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: MonitorsAPI.create_monitor_notification_rule ...'
@@ -317,12 +311,6 @@ def delete_monitor_notification_rule(rule_id, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def delete_monitor_notification_rule_with_http_info(rule_id, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.delete_monitor_notification_rule".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.delete_monitor_notification_rule")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.delete_monitor_notification_rule"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: MonitorsAPI.delete_monitor_notification_rule ...'
@@ -525,12 +513,6 @@ def get_monitor_notification_rule(rule_id, opts = {})
     # @option opts [String] :include Comma-separated list of resource paths for related resources to include in the response. Supported resource path is `created_by`.
     # @return [Array<(MonitorNotificationRuleResponse, Integer, Hash)>] MonitorNotificationRuleResponse data, response status code and response headers
     def get_monitor_notification_rule_with_http_info(rule_id, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.get_monitor_notification_rule".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.get_monitor_notification_rule")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.get_monitor_notification_rule"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: MonitorsAPI.get_monitor_notification_rule ...'
@@ -597,12 +579,6 @@ def get_monitor_notification_rules(opts = {})
     # @option opts [String] :include Comma-separated list of resource paths for related resources to include in the response. Supported resource path is `created_by`.
     # @return [Array<(MonitorNotificationRuleListResponse, Integer, Hash)>] MonitorNotificationRuleListResponse data, response status code and response headers
     def get_monitor_notification_rules_with_http_info(opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.get_monitor_notification_rules".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.get_monitor_notification_rules")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.get_monitor_notification_rules"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: MonitorsAPI.get_monitor_notification_rules ...'
@@ -937,12 +913,6 @@ def update_monitor_notification_rule(rule_id, body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(MonitorNotificationRuleResponse, Integer, Hash)>] MonitorNotificationRuleResponse data, response status code and response headers
     def update_monitor_notification_rule_with_http_info(rule_id, body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.update_monitor_notification_rule".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.update_monitor_notification_rule")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.update_monitor_notification_rule"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: MonitorsAPI.update_monitor_notification_rule ...'

Original file line number	Diff line number	Diff line change
`@@ -4,13 +4,13 @@`
`4`	`4`	`"spec_versions": {`
`5`	`5`	`"v1": {`
`6`	`6`	`"apigentools_version": "1.6.6",`
`7`		`- "regenerated": "2025-07-02 16:34:52.201607",`
`8`		`- "spec_repo_commit": "de2517ad"`
	`7`	`+ "regenerated": "2025-07-02 20:43:20.487037",`
	`8`	`+ "spec_repo_commit": "e327e6df"`
`9`	`9`	`},`
`10`	`10`	`"v2": {`
`11`	`11`	`"apigentools_version": "1.6.6",`
`12`		`- "regenerated": "2025-07-02 16:34:52.217566",`
`13`		`- "spec_repo_commit": "de2517ad"`
	`12`	`+ "regenerated": "2025-07-02 20:43:20.503175",`
	`13`	`+ "spec_repo_commit": "e327e6df"`
`14`	`14`	`}`
`15`	`15`	`}`
`16`	`16`	`}`