Avoid clashes due to id (#2022)

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

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-27 19:28:18.330379",
-            "spec_repo_commit": "4a99b1d3"
+            "regenerated": "2025-01-27 21:19:33.830146",
+            "spec_repo_commit": "aa10e3e1"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-27 19:28:18.346174",
-            "spec_repo_commit": "4a99b1d3"
+            "regenerated": "2025-01-27 21:19:33.846154",
+            "spec_repo_commit": "aa10e3e1"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -22615,6 +22615,7 @@ components:
     Version:
       description: Version of the updated signal. If server side version is higher,
         update will be rejected.
+      example: 0
       format: int64
       type: integer
     WebhooksIntegration:

features/v1/security_monitoring.feature

@@ -13,15 +13,15 @@ Feature: Security Monitoring
   Scenario: Add a security signal to an incident returns "Bad Request" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"incident_id": 2066}
+    And body with value {"incident_id": 2066, "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Add a security signal to an incident returns "Not Found" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"incident_id": 2066}
+    And body with value {"incident_id": 2066, "version": 0}
     When the request is sent
     Then the response status is 404 Not Found
 
@@ -38,15 +38,15 @@ Feature: Security Monitoring
   Scenario: Change the triage state of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"archiveReason": "none", "state": "open"}
+    And body with value {"archiveReason": "none", "state": "open", "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Change the triage state of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"archiveReason": "none", "state": "open"}
+    And body with value {"archiveReason": "none", "state": "open", "version": 0}
     When the request is sent
     Then the response status is 404 Not Found
 
@@ -63,15 +63,15 @@ Feature: Security Monitoring
   Scenario: Modify the triage assignee of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940"}
+    And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Modify the triage assignee of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
-    And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940"}
+    And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
     When the request is sent
     Then the response status is 404 Not Found