Regenerate client from commit 05963a4f of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-06 19:03:03.772449",
-            "spec_repo_commit": "b56ea2d7"
+            "regenerated": "2025-01-07 18:03:24.600912",
+            "spec_repo_commit": "05963a4f"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-06 19:03:03.787661",
-            "spec_repo_commit": "b56ea2d7"
+            "regenerated": "2025-01-07 18:03:24.615901",
+            "spec_repo_commit": "05963a4f"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -36670,10 +36670,14 @@ tags:
     end times, prevent all alerting related to specified Datadog tags.'
   name: Downtimes
 - description: 'The Event Management API allows you to programmatically post events
-    to the Events Explorer
-
-    and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
-    for more information.'
+    to the Events Explorer and fetch events from the Events Explorer. See the [Event
+    Management page](https://docs.datadoghq.com/service_management/events/) for more
+    information. **Update to the aggregation_key for Datadog monitor events:** Currently,
+    the aggregation_key is unique per Monitor ID. Starting March 1st, we will update
+    it to be unique per Monitor ID and Monitor Group. Please reach out to support
+    if you have any question.
+
+    '
   name: Events
 - description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly
 

.generator/schemas/v2/openapi.yaml

@@ -48236,10 +48236,14 @@ tags:
     end times, prevent all alerting related to specified Datadog tags.'
   name: Downtimes
 - description: 'The Event Management API allows you to programmatically post events
-    to the Events Explorer
-
-    and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
-    for more information.'
+    to the Events Explorer and fetch events from the Events Explorer. See the [Event
+    Management page](https://docs.datadoghq.com/service_management/events/) for more
+    information. **Update to the aggregation_key for Datadog monitor events:** Currently,
+    the aggregation_key is unique per Monitor ID. Starting March 1st, we will update
+    it to be unique per Monitor ID and Monitor Group. Please reach out to support
+    if you have any question.
+
+    '
   name: Events
 - description: Manage your Datadog Fastly integration accounts and services directly
     through the Datadog API. See the [Fastly integration page](https://docs.datadoghq.com/integrations/fastly/)

features/v1/events.feature

@@ -3,7 +3,10 @@ Feature: Events
   The Event Management API allows you to programmatically post events to the
   Events Explorer and fetch events from the Events Explorer. See the [Event
   Management page](https://docs.datadoghq.com/service_management/events/)
-  for more information.
+  for more information. **Update to the aggregation_key for Datadog monitor
+  events:** Currently, the aggregation_key is unique per Monitor ID.
+  Starting March 1st, we will update it to be unique per Monitor ID and
+  Monitor Group. Please reach out to support if you have any question.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

features/v2/events.feature

@@ -3,7 +3,10 @@ Feature: Events
   The Event Management API allows you to programmatically post events to the
   Events Explorer and fetch events from the Events Explorer. See the [Event
   Management page](https://docs.datadoghq.com/service_management/events/)
-  for more information.
+  for more information. **Update to the aggregation_key for Datadog monitor
+  events:** Currently, the aggregation_key is unique per Monitor ID.
+  Starting March 1st, we will update it to be unique per Monitor ID and
+  Monitor Group. Please reach out to support if you have any question.
 
   Background:
     Given a valid "apiKeyAuth" key in the system