Add rule type conversion limitations for Security Monitoring (#1024)

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

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

.generator/schemas/v2/openapi.yaml

@@ -79133,9 +79133,20 @@ paths:
   /api/v2/security_monitoring/rules/convert:
     post:
       description: 'Convert a rule that doesn''t (yet) exist from JSON to Terraform
-        for datadog provider
+        for Datadog provider
 
-        resource datadog_security_monitoring_rule.'
+        resource `datadog_security_monitoring_rule`. You can do so for the following
+        rule types:
+
+        - App and API Protection
+
+        - Cloud SIEM (log detection and signal correlation)
+
+        - Workload Protection
+
+
+        You can convert Cloud Security configuration rules using Terraform''s [Datadog
+        Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
       operationId: ConvertSecurityMonitoringRuleFromJSONToTerraform
       requestBody:
         content:
@@ -79352,9 +79363,20 @@ paths:
         - security_monitoring_rules_write
   /api/v2/security_monitoring/rules/{rule_id}/convert:
     get:
-      description: 'Convert an existing rule from JSON to Terraform for datadog provider
+      description: 'Convert an existing rule from JSON to Terraform for Datadog provider
+
+        resource `datadog_security_monitoring_rule`. You can do so for the following
+        rule types:
+
+        - App and API Protection
+
+        - Cloud SIEM (log detection and signal correlation)
+
+        - Workload Protection
+
 
-        resource datadog_security_monitoring_rule.'
+        You can convert Cloud Security configuration rules using Terraform''s [Datadog
+        Cloud Configuration Rule resource](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule).'
       operationId: ConvertExistingSecurityMonitoringRule
       parameters:
       - $ref: '#/components/parameters/SecurityMonitoringRuleID'

src/datadogV2/api/api_security_monitoring.rs

@@ -1743,8 +1743,13 @@ impl SecurityMonitoringAPI {
         }
     }
 
-    /// Convert an existing rule from JSON to Terraform for datadog provider
-    /// resource datadog_security_monitoring_rule.
+    /// Convert an existing rule from JSON to Terraform for Datadog provider
+    /// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
+    /// - App and API Protection
+    /// - Cloud SIEM (log detection and signal correlation)
+    /// - Workload Protection
+    ///
+    /// You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](<https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule>).
     pub async fn convert_existing_security_monitoring_rule(
         &self,
         rule_id: String,
@@ -1769,8 +1774,13 @@ impl SecurityMonitoringAPI {
         }
     }
 
-    /// Convert an existing rule from JSON to Terraform for datadog provider
-    /// resource datadog_security_monitoring_rule.
+    /// Convert an existing rule from JSON to Terraform for Datadog provider
+    /// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
+    /// - App and API Protection
+    /// - Cloud SIEM (log detection and signal correlation)
+    /// - Workload Protection
+    ///
+    /// You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](<https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule>).
     pub async fn convert_existing_security_monitoring_rule_with_http_info(
         &self,
         rule_id: String,
@@ -1999,8 +2009,13 @@ impl SecurityMonitoringAPI {
         }
     }
 
-    /// Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
-    /// resource datadog_security_monitoring_rule.
+    /// Convert a rule that doesn't (yet) exist from JSON to Terraform for Datadog provider
+    /// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
+    /// - App and API Protection
+    /// - Cloud SIEM (log detection and signal correlation)
+    /// - Workload Protection
+    ///
+    /// You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](<https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule>).
     pub async fn convert_security_monitoring_rule_from_json_to_terraform(
         &self,
         body: crate::datadogV2::model::SecurityMonitoringRuleConvertPayload,
@@ -2025,8 +2040,13 @@ impl SecurityMonitoringAPI {
         }
     }
 
-    /// Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider
-    /// resource datadog_security_monitoring_rule.
+    /// Convert a rule that doesn't (yet) exist from JSON to Terraform for Datadog provider
+    /// resource `datadog_security_monitoring_rule`. You can do so for the following rule types:
+    /// - App and API Protection
+    /// - Cloud SIEM (log detection and signal correlation)
+    /// - Workload Protection
+    ///
+    /// You can convert Cloud Security configuration rules using Terraform's [Datadog Cloud Configuration Rule resource](<https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/cloud_configuration_rule>).
     pub async fn convert_security_monitoring_rule_from_json_to_terraform_with_http_info(
         &self,
         body: crate::datadogV2::model::SecurityMonitoringRuleConvertPayload,