Regenerate client from commit 2d73b65d of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-10 18:01:24.451821",
-            "spec_repo_commit": "c0a45137"
+            "regenerated": "2025-04-10 20:09:26.549571",
+            "spec_repo_commit": "2d73b65d"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-10 18:01:24.467888",
-            "spec_repo_commit": "c0a45137"
+            "regenerated": "2025-04-10 20:09:26.565987",
+            "spec_repo_commit": "2d73b65d"
         }
     }
 }

cassettes/features/v2/incidents/Create-an-incident-type-returns-CREATED-response.frozen

@@ -1 +1 @@
-2024-11-04T19:02:20.402Z
+2025-04-09T20:37:29.894Z

cassettes/features/v2/incidents/Create-an-incident-type-returns-CREATED-response.yml

@@ -1 +1 @@
-2024-11-04T19:02:22.569Z
+2025-04-09T20:37:30.425Z

cassettes/features/v2/incidents/Delete-an-incident-type-returns-OK-response.frozen

@@ -1 +1 @@
-2024-11-04T19:02:38.662Z
+2025-04-09T20:37:30.806Z

cassettes/features/v2/incidents/Delete-an-incident-type-returns-OK-response.yml

@@ -11,7 +11,7 @@
     attributes: DatadogAPIClient::V2::IncidentTypeAttributes.new({
       description: "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.",
       is_default: false,
-      name: "Security Incident",
+      name: "8d4bbb66dccf2456",
     }),
     type: DatadogAPIClient::V2::IncidentTypeType::INCIDENT_TYPES,
   }),

cassettes/features/v2/incidents/Update-an-incident-type-returns-OK-response.frozen

@@ -196,7 +196,7 @@
     "parameters": [
       {
         "name": "body",
-        "value": "{\n  \"data\": {\n    \"attributes\": {\n      \"name\": \"Security Incident\",\n      \"description\": \"Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.\",\n      \"is_default\": false\n    },\n    \"type\": \"incident_types\"\n  }\n}"
+        "value": "{\n  \"data\": {\n    \"attributes\": {\n      \"name\": \"{{ unique_hash }}\",\n      \"description\": \"Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.\",\n      \"is_default\": false\n    },\n    \"type\": \"incident_types\"\n  }\n}"
       }
     ],
     "step": "there is a valid \"incident_type\" in the system",

cassettes/features/v2/incidents/Update-an-incident-type-returns-OK-response.yml

@@ -134,7 +134,7 @@ Feature: Incidents
   Scenario: Create an incident type returns "CREATED" response
     Given operation "CreateIncidentType" enabled
     And new "CreateIncidentType" request
-    And body with value {"data": {"attributes": {"description": "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.", "is_default": false, "name": "Security Incident"}, "type": "incident_types"}}
+    And body with value {"data": {"attributes": {"description": "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.", "is_default": false, "name": "{{ unique_hash }}"}, "type": "incident_types"}}
     When the request is sent
     Then the response status is 201 CREATED