Skip to content

Commit

Permalink
Regenerate client from commit 4bbb9d73 of spec repo
Browse files Browse the repository at this point in the history
  • Loading branch information
ci.datadog-api-spec committed Jan 8, 2025
1 parent a4d1f50 commit 0ecedd8
Show file tree
Hide file tree
Showing 5 changed files with 32 additions and 16 deletions.
8 changes: 4 additions & 4 deletions .apigentools-info
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@
"spec_versions": {
"v1": {
"apigentools_version": "1.6.6",
"regenerated": "2025-01-08 14:02:30.066418",
"spec_repo_commit": "1920836f"
"regenerated": "2025-01-08 22:15:07.990279",
"spec_repo_commit": "4bbb9d73"
},
"v2": {
"apigentools_version": "1.6.6",
"regenerated": "2025-01-08 14:02:30.082176",
"spec_repo_commit": "1920836f"
"regenerated": "2025-01-08 22:15:08.005535",
"spec_repo_commit": "4bbb9d73"
}
}
}
13 changes: 8 additions & 5 deletions .generator/schemas/v1/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36664,11 +36664,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.'
- 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.\n\n**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. If you\u2019re using
monitor events aggregation_key in dashboard queries or the Event API, please migrate
to using @monitor.id. Please reach out to support if you have any question."
name: Events
- description: 'Configure your Datadog-Google Cloud Platform (GCP) integration directly

Expand Down
13 changes: 8 additions & 5 deletions .generator/schemas/v2/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -48309,11 +48309,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.'
- 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.\n**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. If you\u2019re using monitor
events aggregation_key in dashboard queries or the Event API, please migrate to
using @monitor.id. Please reach out to support if you have any question.\n"
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/)
Expand Down
7 changes: 6 additions & 1 deletion tests/scenarios/features/v1/events.feature
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,12 @@ 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. If you’re using monitor events aggregation_key in dashboard
queries or the Event API, please migrate to using @monitor.id. Please
reach out to support if you have any question.

Background:
Given a valid "apiKeyAuth" key in the system
Expand Down
7 changes: 6 additions & 1 deletion tests/scenarios/features/v2/events.feature
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,12 @@ 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. If you’re using monitor events aggregation_key in dashboard
queries or the Event API, please migrate to using @monitor.id. Please
reach out to support if you have any question.

Background:
Given a valid "apiKeyAuth" key in the system
Expand Down

0 comments on commit 0ecedd8

Please sign in to comment.