From 946c12a9688e86d9a322583d0cd7426ea7b823a7 Mon Sep 17 00:00:00 2001
From: "ci.datadog-api-spec" <packages@datadoghq.com>
Date: Wed, 12 Nov 2025 21:10:15 +0000
Subject: [PATCH] Regenerate client from commit 199abc9 of spec repo

---
 .generator/schemas/v2/openapi.yaml            | 26 +++++++++++++++++--
 .../src/v2/SecurityMonitoringApi.ts           | 14 ++++++++--
 2 files changed, 36 insertions(+), 4 deletions(-)

diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index f9a4ea8590d2..2fc656b1441e 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -77969,7 +77969,18 @@ paths:
       description: 'Convert a rule that doesn''t (yet) exist from JSON to Terraform
         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:
@@ -78188,7 +78199,18 @@ paths:
     get:
       description: 'Convert an existing rule from JSON to Terraform 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: ConvertExistingSecurityMonitoringRule
       parameters:
       - $ref: '#/components/parameters/SecurityMonitoringRuleID'
diff --git a/services/security_monitoring/src/v2/SecurityMonitoringApi.ts b/services/security_monitoring/src/v2/SecurityMonitoringApi.ts
index 147d0793929d..b8f6a2bf99e4 100644
--- a/services/security_monitoring/src/v2/SecurityMonitoringApi.ts
+++ b/services/security_monitoring/src/v2/SecurityMonitoringApi.ts
@@ -9688,7 +9688,12 @@ export class SecurityMonitoringApi {
 
   /**
    * Convert an existing rule from JSON to Terraform 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).
    * @param param The request object
    */
   public convertExistingSecurityMonitoringRule(
@@ -9736,7 +9741,12 @@ export class SecurityMonitoringApi {
 
   /**
    * Convert a rule that doesn't (yet) exist from JSON to Terraform 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).
    * @param param The request object
    */
   public convertSecurityMonitoringRuleFromJSONToTerraform(