Regenerate client from commit 50ef9d5 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -64883,7 +64883,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/SecurityMonitoringSuppressionUpdateRequest'
+              $ref: '#/components/schemas/SecurityMonitoringSuppressionCreateRequest'
         required: true
       responses:
         '204':

examples/v2_security-monitoring_ValidateSecurityMonitoringSuppression.rs

@@ -1,24 +1,24 @@
 // Validate a suppression rule returns "OK" response
 use datadog_api_client::datadog;
 use datadog_api_client::datadogV2::api_security_monitoring::SecurityMonitoringAPI;
+use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionCreateAttributes;
+use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionCreateData;
+use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionCreateRequest;
 use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionType;
-use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionUpdateAttributes;
-use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionUpdateData;
-use datadog_api_client::datadogV2::model::SecurityMonitoringSuppressionUpdateRequest;
 
 #[tokio::main]
 async fn main() {
-    let body = SecurityMonitoringSuppressionUpdateRequest::new(
-        SecurityMonitoringSuppressionUpdateData::new(
-            SecurityMonitoringSuppressionUpdateAttributes::new()
-                .data_exclusion_query("source:cloudtrail account_id:12345".to_string())
-                .description(
-                    "This rule suppresses low-severity signals in staging environments."
-                        .to_string(),
-                )
-                .enabled(true)
-                .name("Custom suppression".to_string())
-                .rule_query("type:log_detection source:cloudtrail".to_string()),
+    let body = SecurityMonitoringSuppressionCreateRequest::new(
+        SecurityMonitoringSuppressionCreateData::new(
+            SecurityMonitoringSuppressionCreateAttributes::new(
+                true,
+                "Custom suppression".to_string(),
+                "type:log_detection source:cloudtrail".to_string(),
+            )
+            .data_exclusion_query("source:cloudtrail account_id:12345".to_string())
+            .description(
+                "This rule suppresses low-severity signals in staging environments.".to_string(),
+            ),
             SecurityMonitoringSuppressionType::SUPPRESSIONS,
         ),
     );

src/datadogV2/api/api_security_monitoring.rs

@@ -10747,7 +10747,7 @@ impl SecurityMonitoringAPI {
     /// Validate a suppression rule.
     pub async fn validate_security_monitoring_suppression(
         &self,
-        body: crate::datadogV2::model::SecurityMonitoringSuppressionUpdateRequest,
+        body: crate::datadogV2::model::SecurityMonitoringSuppressionCreateRequest,
     ) -> Result<(), datadog::Error<ValidateSecurityMonitoringSuppressionError>> {
         match self
             .validate_security_monitoring_suppression_with_http_info(body)
@@ -10761,7 +10761,7 @@ impl SecurityMonitoringAPI {
     /// Validate a suppression rule.
     pub async fn validate_security_monitoring_suppression_with_http_info(
         &self,
-        body: crate::datadogV2::model::SecurityMonitoringSuppressionUpdateRequest,
+        body: crate::datadogV2::model::SecurityMonitoringSuppressionCreateRequest,
     ) -> Result<
         datadog::ResponseContent<()>,
         datadog::Error<ValidateSecurityMonitoringSuppressionError>,

tests/scenarios/cassettes/v2/security_monitoring/Validate-a-suppression-rule-returns-Bad-Request-response.frozen

@@ -1 +1 @@
-2025-09-01T21:36:42.334Z
+2025-09-04T08:33:38.344Z

tests/scenarios/cassettes/v2/security_monitoring/Validate-a-suppression-rule-returns-Bad-Request-response.json

@@ -3,7 +3,7 @@
     {
       "request": {
         "body": {
-          "string": "{\"data\":{\"attributes\":{\"data_exclusion_query\":\"not enough attributes\"},\"type\":\"suppressions\"}}",
+          "string": "{\"data\":{\"attributes\":{\"data_exclusion_query\":\"not enough attributes\",\"enabled\":false,\"name\":\"cold_harbour\",\"rule_query\":\"rule:[A-Invalid\"},\"type\":\"suppressions\"}}",
           "encoding": null
         },
         "headers": {
@@ -19,7 +19,7 @@
       },
       "response": {
         "body": {
-          "string": "{\"errors\":[\"input_validation_error(Field 'data.attributes.rule_query' is invalid: field 'rule_query' is required)\",\"input_validation_error(Field 'data.attributes.name' is invalid: name cannot be empty)\"]}",
+          "string": "{\"errors\":[\"input_validation_error(Field 'data.attributes.rule_query' is invalid: rule query is invalid)\"]}",
           "encoding": null
         },
         "headers": {
@@ -32,7 +32,7 @@
           "message": "Bad Request"
         }
       },
-      "recorded_at": "Mon, 01 Sep 2025 21:36:42 GMT"
+      "recorded_at": "Thu, 04 Sep 2025 08:33:38 GMT"
     }
   ],
   "recorded_with": "VCR 6.0.0"

tests/scenarios/features/v2/security_monitoring.feature

@@ -1486,7 +1486,7 @@ Feature: Security Monitoring
   @team:DataDog/k9-cloud-security-platform
   Scenario: Validate a suppression rule returns "Bad Request" response
     Given new "ValidateSecurityMonitoringSuppression" request
-    And body with value {"data": {"attributes": {"data_exclusion_query": "not enough attributes"}, "type": "suppressions"}}
+    And body with value {"data": {"attributes": {"name" : "cold_harbour", "enabled": false, "rule_query":"rule:[A-Invalid", "data_exclusion_query": "not enough attributes"}, "type": "suppressions"}}
     When the request is sent
     Then the response status is 400 Bad Request