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

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

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'

lib/datadog_api_client/v2/api/security_monitoring_api.rb

@@ -104,8 +104,13 @@ def convert_existing_security_monitoring_rule(rule_id, opts = {})
 
     # Convert an existing rule from JSON to Terraform.
     #
-    # 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 rule_id [String] The ID of the rule.
     # @param opts [Hash] the optional parameters
@@ -243,8 +248,13 @@ def convert_security_monitoring_rule_from_json_to_terraform(body, opts = {})
 
     # Convert a rule from JSON to Terraform.
     #
-    # 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 body [SecurityMonitoringRuleConvertPayload] 
     # @param opts [Hash] the optional parameters