Regenerate client from commit 8d40e082 of spec repo

ci.datadog-api-spec · ci.datadog-api-spec · commit db8f8da029b8 · 2025-01-09T22:11:28.000Z
diff --git a/.apigentools-info b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-09 21:08:27.091214",
-            "spec_repo_commit": "435429e0"
+            "regenerated": "2025-01-09 22:06:04.168404",
+            "spec_repo_commit": "8d40e082"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-09 21:08:27.107621",
-            "spec_repo_commit": "435429e0"
+            "regenerated": "2025-01-09 22:06:04.183707",
+            "spec_repo_commit": "8d40e082"
         }
     }
 }
diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml
@@ -36666,10 +36666,17 @@ 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
+    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.
 
-    and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
-    for more information.'
+
+    **Update to Datadog monitor events `aggregation_key` starting March 1, 2025:**
+    The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting
+    March 1st, this key will also include Monitor Group, making it unique per *Monitor
+    ID and Monitor Group*. If you''re using monitor events `aggregation_key` in dashboard
+    queries or the Event API, you must migrate to use `@monitor.id`. Reach out to
+    [support](https://www.datadoghq.com/support/) if you have any question.'
   name: Events
 - description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly
 
diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
@@ -48310,10 +48310,17 @@ 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
+    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.
 
-    and fetch events from the Events Explorer. See the [Event Management page](https://docs.datadoghq.com/service_management/events/)
-    for more information.'
+
+    **Update to Datadog monitor events `aggregation_key` starting March 1, 2025:**
+    The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting
+    March 1st, this key will also include Monitor Group, making it unique per *Monitor
+    ID and Monitor Group*. If you''re using monitor events `aggregation_key` in dashboard
+    queries or the Event API, you must migrate to use `@monitor.id`. Reach out to
+    [support](https://www.datadoghq.com/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/)
diff --git a/src/datadogV1/api/api_events.rs b/src/datadogV1/api/api_events.rs
@@ -93,8 +93,9 @@ pub enum ListEventsError {
     UnknownValue(serde_json::Value),
 }
 
-/// 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.
+/// 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.
+///
+/// **Update to Datadog monitor events `aggregation_key` starting March 1, 2025:** The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting March 1st, this key will also include Monitor Group, making it unique per *Monitor ID and Monitor Group*. If you're using monitor events `aggregation_key` in dashboard queries or the Event API, you must migrate to use `@monitor.id`. Reach out to [support](<https://www.datadoghq.com/support/>) if you have any question.
 #[derive(Debug, Clone)]
 pub struct EventsAPI {
     config: datadog::Configuration,
diff --git a/src/datadogV2/api/api_events.rs b/src/datadogV2/api/api_events.rs
@@ -102,8 +102,9 @@ pub enum SearchEventsError {
     UnknownValue(serde_json::Value),
 }
 
-/// 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.
+/// 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.
+///
+/// **Update to Datadog monitor events `aggregation_key` starting March 1, 2025:** The Datadog monitor events `aggregation_key` is unique to each Monitor ID. Starting March 1st, this key will also include Monitor Group, making it unique per *Monitor ID and Monitor Group*. If you're using monitor events `aggregation_key` in dashboard queries or the Event API, you must migrate to use `@monitor.id`. Reach out to [support](<https://www.datadoghq.com/support/>) if you have any question.
 #[derive(Debug, Clone)]
 pub struct EventsAPI {
     config: datadog::Configuration,
diff --git a/tests/scenarios/features/v1/events.feature b/tests/scenarios/features/v1/events.feature
@@ -3,7 +3,14 @@ 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 Datadog monitor events
+  `aggregation_key` starting March 1, 2025:** The Datadog monitor events
+  `aggregation_key` is unique to each Monitor ID. Starting March 1st, this
+  key will also include Monitor Group, making it unique per *Monitor ID and
+  Monitor Group*. If you're using monitor events `aggregation_key` in
+  dashboard queries or the Event API, you must migrate to use `@monitor.id`.
+  Reach out to [support](https://www.datadoghq.com/support/) if you have any
+  question.
 
   Background:
     Given a valid "apiKeyAuth" key in the system
diff --git a/tests/scenarios/features/v2/events.feature b/tests/scenarios/features/v2/events.feature
@@ -3,7 +3,14 @@ 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 Datadog monitor events
+  `aggregation_key` starting March 1, 2025:** The Datadog monitor events
+  `aggregation_key` is unique to each Monitor ID. Starting March 1st, this
+  key will also include Monitor Group, making it unique per *Monitor ID and
+  Monitor Group*. If you're using monitor events `aggregation_key` in
+  dashboard queries or the Event API, you must migrate to use `@monitor.id`.
+  Reach out to [support](https://www.datadoghq.com/support/) if you have any
+  question.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

Original file line number	Diff line number	Diff line change
`@@ -4,13 +4,13 @@`
`4`	`4`	`"spec_versions": {`
`5`	`5`	`"v1": {`
`6`	`6`	`"apigentools_version": "1.6.6",`
`7`		`- "regenerated": "2025-01-09 21:08:27.091214",`
`8`		`- "spec_repo_commit": "435429e0"`
	`7`	`+ "regenerated": "2025-01-09 22:06:04.168404",`
	`8`	`+ "spec_repo_commit": "8d40e082"`
`9`	`9`	`},`
`10`	`10`	`"v2": {`
`11`	`11`	`"apigentools_version": "1.6.6",`
`12`		`- "regenerated": "2025-01-09 21:08:27.107621",`
`13`		`- "spec_repo_commit": "435429e0"`
	`12`	`+ "regenerated": "2025-01-09 22:06:04.183707",`
	`13`	`+ "spec_repo_commit": "8d40e082"`
`14`	`14`	`}`
`15`	`15`	`}`
`16`	`16`	`}`