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

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'

services/security_monitoring/src/v2/SecurityMonitoringApi.ts

@@ -9687,8 +9687,13 @@ export class 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).
    * @param param The request object
    */
   public convertExistingSecurityMonitoringRule(
@@ -9735,8 +9740,13 @@ export class 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).
    * @param param The request object
    */
   public convertSecurityMonitoringRuleFromJSONToTerraform(