From 8ea1493e0580be3d5a3732fac273c659a8ef5c71 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Thu, 9 Jan 2025 21:10:53 +0000 Subject: [PATCH] Regenerate client from commit 618968b6 of spec repo --- .apigentools-info | 8 ++++---- .generator/schemas/v1/openapi.yaml | 13 ++++++++++--- .generator/schemas/v2/openapi.yaml | 13 ++++++++++--- src/datadog_api_client/v1/api/events_api.py | 5 +++-- src/datadog_api_client/v2/api/events_api.py | 5 +++-- tests/v1/features/events.feature | 9 ++++++++- tests/v2/features/events.feature | 9 ++++++++- 7 files changed, 46 insertions(+), 16 deletions(-) diff --git a/.apigentools-info b/.apigentools-info index 229ac1a23e..0acd692873 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 20:03:44.763258", - "spec_repo_commit": "07ed2f56" + "regenerated": "2025-01-09 21:10:19.691829", + "spec_repo_commit": "618968b6" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2025-01-09 20:03:44.778099", - "spec_repo_commit": "07ed2f56" + "regenerated": "2025-01-09 21:10:19.707558", + "spec_repo_commit": "618968b6" } } } \ No newline at end of file diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml index e810c23508..0cebc8b7c5 100644 --- a/.generator/schemas/v1/openapi.yaml +++ b/.generator/schemas/v1/openapi.yaml @@ -36665,10 +36665,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 fadab8d3ec..7e519f9265 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/src/datadog_api_client/v1/api/events_api.py b/src/datadog_api_client/v1/api/events_api.py index 2b404bfd98..bb6b80d6ee 100644 --- a/src/datadog_api_client/v1/api/events_api.py +++ b/src/datadog_api_client/v1/api/events_api.py @@ -20,8 +20,9 @@ class EventsApi: """ - 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 `_ 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 `_ 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 `_ if you have any question. """ def __init__(self, api_client=None): diff --git a/src/datadog_api_client/v2/api/events_api.py b/src/datadog_api_client/v2/api/events_api.py index 383e48fd8f..1be946ba3c 100644 --- a/src/datadog_api_client/v2/api/events_api.py +++ b/src/datadog_api_client/v2/api/events_api.py @@ -24,8 +24,9 @@ class EventsApi: """ - 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 `_ 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 `_ 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 `_ if you have any question. """ def __init__(self, api_client=None): diff --git a/tests/v1/features/events.feature b/tests/v1/features/events.feature index 3005fc756f..e1b7d8a0fd 100644 --- a/tests/v1/features/events.feature +++ b/tests/v1/features/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/v2/features/events.feature b/tests/v2/features/events.feature index eada249fd8..61310eb2c6 100644 --- a/tests/v2/features/events.feature +++ b/tests/v2/features/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