From d211759a109a94e3a44e1f91e86a76fe55cfe0f3 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Thu, 9 Jan 2025 22:07:40 +0000 Subject: [PATCH] Regenerate client from commit 8d40e082 of spec repo --- .apigentools-info | 8 ++++---- .generator/schemas/v1/openapi.yaml | 13 ++++++++++--- .generator/schemas/v2/openapi.yaml | 13 ++++++++++--- features/v1/events.feature | 9 ++++++++- features/v2/events.feature | 9 ++++++++- 5 files changed, 40 insertions(+), 12 deletions(-) diff --git a/.apigentools-info b/.apigentools-info index 3514a32b044b..73dd863d9463 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 21:08:21.064628", - "spec_repo_commit": "435429e0" + "regenerated": "2025-01-09 22:06:12.202192", + "spec_repo_commit": "8d40e082" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 21:08:21.079610", - "spec_repo_commit": "435429e0" + "regenerated": "2025-01-09 22:06:12.217985", + "spec_repo_commit": "8d40e082" } } } \ No newline at end of file diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml index c2af523e94cd..09a4d845e5ff 100644 --- 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 index fadab8d3ec6e..7e519f92653b 100644 --- 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/features/v1/events.feature b/features/v1/events.feature index 3005fc756fb8..e1b7d8a0fd62 100644 --- a/features/v1/events.feature +++ b/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/features/v2/events.feature b/features/v2/events.feature index eada249fd880..61310eb2c6f9 100644 --- a/features/v2/events.feature +++ b/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