Skip to content

Commit 38b4460

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit f1b97e5 of spec repo
1 parent 6ee12bc commit 38b4460

24 files changed

Lines changed: 2450 additions & 20 deletions

‎.generator/schemas/v2/openapi.yaml‎

Lines changed: 472 additions & 0 deletions
Large diffs are not rendered by default.

‎features/v2/incidents.feature‎

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,33 @@ Feature: Incidents
2121
When the request is sent
2222
Then the response status is 200 OK
2323

24+
@generated @skip @team:Datadog/incident-app
25+
Scenario: Create a timestamp override for an incident returns "Bad Request" response
26+
Given operation "CreateIncidentTimestampOverride" enabled
27+
And new "CreateIncidentTimestampOverride" request
28+
And request contains "incident_id" parameter from "REPLACE.ME"
29+
And body with value {"data": {"attributes": {"timestamp_type": "created", "timestamp_value": "2024-12-29T10:00:00Z"}, "type": "incidents_timestamp_overrides"}}
30+
When the request is sent
31+
Then the response status is 400 Bad Request
32+
33+
@generated @skip @team:Datadog/incident-app
34+
Scenario: Create a timestamp override for an incident returns "Created" response
35+
Given operation "CreateIncidentTimestampOverride" enabled
36+
And new "CreateIncidentTimestampOverride" request
37+
And request contains "incident_id" parameter from "REPLACE.ME"
38+
And body with value {"data": {"attributes": {"timestamp_type": "created", "timestamp_value": "2024-12-29T10:00:00Z"}, "type": "incidents_timestamp_overrides"}}
39+
When the request is sent
40+
Then the response status is 201 Created
41+
42+
@generated @skip @team:Datadog/incident-app
43+
Scenario: Create a timestamp override for an incident returns "Not Found" response
44+
Given operation "CreateIncidentTimestampOverride" enabled
45+
And new "CreateIncidentTimestampOverride" request
46+
And request contains "incident_id" parameter from "REPLACE.ME"
47+
And body with value {"data": {"attributes": {"timestamp_type": "created", "timestamp_value": "2024-12-29T10:00:00Z"}, "type": "incidents_timestamp_overrides"}}
48+
When the request is sent
49+
Then the response status is 404 Not Found
50+
2451
@skip @team:DataDog/incident-app
2552
Scenario: Create an incident impact returns "Bad Request" response
2653
Given operation "CreateIncidentImpact" enabled
@@ -330,6 +357,24 @@ Feature: Incidents
330357
When the request is sent
331358
Then the response status is 404 Not Found
332359

360+
@generated @skip @team:Datadog/incident-app
361+
Scenario: Delete a timestamp override for an incident returns "No Content" response
362+
Given operation "DeleteIncidentTimestampOverride" enabled
363+
And new "DeleteIncidentTimestampOverride" request
364+
And request contains "incident_id" parameter from "REPLACE.ME"
365+
And request contains "timestamp_override_id" parameter from "REPLACE.ME"
366+
When the request is sent
367+
Then the response status is 204 No Content
368+
369+
@generated @skip @team:Datadog/incident-app
370+
Scenario: Delete a timestamp override for an incident returns "Not Found" response
371+
Given operation "DeleteIncidentTimestampOverride" enabled
372+
And new "DeleteIncidentTimestampOverride" request
373+
And request contains "incident_id" parameter from "REPLACE.ME"
374+
And request contains "timestamp_override_id" parameter from "REPLACE.ME"
375+
When the request is sent
376+
Then the response status is 404 Not Found
377+
333378
@generated @skip @team:DataDog/incident-app
334379
Scenario: Delete an existing incident returns "Bad Request" response
335380
Given operation "DeleteIncident" enabled
@@ -1018,6 +1063,22 @@ Feature: Incidents
10181063
When the request is sent
10191064
Then the response status is 200 OK
10201065

1066+
@generated @skip @team:Datadog/incident-app
1067+
Scenario: List timestamp overrides for an incident returns "Not Found" response
1068+
Given operation "ListIncidentTimestampOverrides" enabled
1069+
And new "ListIncidentTimestampOverrides" request
1070+
And request contains "incident_id" parameter from "REPLACE.ME"
1071+
When the request is sent
1072+
Then the response status is 404 Not Found
1073+
1074+
@generated @skip @team:Datadog/incident-app
1075+
Scenario: List timestamp overrides for an incident returns "OK" response
1076+
Given operation "ListIncidentTimestampOverrides" enabled
1077+
And new "ListIncidentTimestampOverrides" request
1078+
And request contains "incident_id" parameter from "REPLACE.ME"
1079+
When the request is sent
1080+
Then the response status is 200 OK
1081+
10211082
@team:DataDog/incident-app
10221083
Scenario: Remove commander from an incident returns "OK" response
10231084
Given operation "UpdateIncident" enabled
@@ -1066,6 +1127,36 @@ Feature: Incidents
10661127
Then the response status is 200 OK
10671128
And the response has 3 items
10681129

1130+
@generated @skip @team:Datadog/incident-app
1131+
Scenario: Update a timestamp override for an incident returns "Bad Request" response
1132+
Given operation "UpdateIncidentTimestampOverride" enabled
1133+
And new "UpdateIncidentTimestampOverride" request
1134+
And request contains "incident_id" parameter from "REPLACE.ME"
1135+
And request contains "timestamp_override_id" parameter from "REPLACE.ME"
1136+
And body with value {"data": {"attributes": {"timestamp_value": "2024-12-29T11:00:00Z"}, "type": "incidents_timestamp_overrides"}}
1137+
When the request is sent
1138+
Then the response status is 400 Bad Request
1139+
1140+
@generated @skip @team:Datadog/incident-app
1141+
Scenario: Update a timestamp override for an incident returns "Not Found" response
1142+
Given operation "UpdateIncidentTimestampOverride" enabled
1143+
And new "UpdateIncidentTimestampOverride" request
1144+
And request contains "incident_id" parameter from "REPLACE.ME"
1145+
And request contains "timestamp_override_id" parameter from "REPLACE.ME"
1146+
And body with value {"data": {"attributes": {"timestamp_value": "2024-12-29T11:00:00Z"}, "type": "incidents_timestamp_overrides"}}
1147+
When the request is sent
1148+
Then the response status is 404 Not Found
1149+
1150+
@generated @skip @team:Datadog/incident-app
1151+
Scenario: Update a timestamp override for an incident returns "OK" response
1152+
Given operation "UpdateIncidentTimestampOverride" enabled
1153+
And new "UpdateIncidentTimestampOverride" request
1154+
And request contains "incident_id" parameter from "REPLACE.ME"
1155+
And request contains "timestamp_override_id" parameter from "REPLACE.ME"
1156+
And body with value {"data": {"attributes": {"timestamp_value": "2024-12-29T11:00:00Z"}, "type": "incidents_timestamp_overrides"}}
1157+
When the request is sent
1158+
Then the response status is 200 OK
1159+
10691160
@generated @skip @team:DataDog/incident-app
10701161
Scenario: Update an existing incident integration metadata returns "Bad Request" response
10711162
Given operation "UpdateIncidentIntegration" enabled

‎features/v2/undo.json‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2013,6 +2013,30 @@
20132013
"type": "idempotent"
20142014
}
20152015
},
2016+
"ListIncidentTimestampOverrides": {
2017+
"tag": "Incidents",
2018+
"undo": {
2019+
"type": "safe"
2020+
}
2021+
},
2022+
"CreateIncidentTimestampOverride": {
2023+
"tag": "Incidents",
2024+
"undo": {
2025+
"type": "unsafe"
2026+
}
2027+
},
2028+
"DeleteIncidentTimestampOverride": {
2029+
"tag": "Incidents",
2030+
"undo": {
2031+
"type": "idempotent"
2032+
}
2033+
},
2034+
"UpdateIncidentTimestampOverride": {
2035+
"tag": "Incidents",
2036+
"undo": {
2037+
"type": "idempotent"
2038+
}
2039+
},
20162040
"ListAWSAccounts": {
20172041
"tag": "AWS Integration",
20182042
"undo": {

‎private/bdd_runner/src/support/scenarios_model_mapping.ts‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6475,6 +6475,66 @@ export const ScenariosModelMappings: { [key: string]: OperationMapping } = {
64756475
},
64766476
operationResponseType: "IncidentTodoResponse",
64776477
},
6478+
"IncidentsApi.V2.ListIncidentTimestampOverrides": {
6479+
incidentId: {
6480+
type: "string",
6481+
format: "uuid",
6482+
},
6483+
include: {
6484+
type: "string",
6485+
format: "",
6486+
},
6487+
includeDeleted: {
6488+
type: "boolean",
6489+
format: "",
6490+
},
6491+
operationResponseType: "IncidentTimestampOverridesResponse",
6492+
},
6493+
"IncidentsApi.V2.CreateIncidentTimestampOverride": {
6494+
incidentId: {
6495+
type: "string",
6496+
format: "uuid",
6497+
},
6498+
include: {
6499+
type: "string",
6500+
format: "",
6501+
},
6502+
body: {
6503+
type: "IncidentTimestampOverrideCreateRequest",
6504+
format: "",
6505+
},
6506+
operationResponseType: "IncidentTimestampOverrideResponse",
6507+
},
6508+
"IncidentsApi.V2.DeleteIncidentTimestampOverride": {
6509+
incidentId: {
6510+
type: "string",
6511+
format: "uuid",
6512+
},
6513+
timestampOverrideId: {
6514+
type: "string",
6515+
format: "uuid",
6516+
},
6517+
operationResponseType: "{}",
6518+
},
6519+
"IncidentsApi.V2.UpdateIncidentTimestampOverride": {
6520+
incidentId: {
6521+
type: "string",
6522+
format: "uuid",
6523+
},
6524+
timestampOverrideId: {
6525+
type: "string",
6526+
format: "uuid",
6527+
},
6528+
include: {
6529+
type: "string",
6530+
format: "",
6531+
},
6532+
body: {
6533+
type: "IncidentTimestampOverridePatchRequest",
6534+
format: "",
6535+
},
6536+
operationResponseType: "IncidentTimestampOverrideResponse",
6537+
},
64786538
"AWSIntegrationApi.V2.ListAWSAccounts": {
64796539
awsAccountId: {
64806540
type: "string",

0 commit comments

Comments
 (0)