Skip to content

Commit cddbe3f

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 588d685e of spec repo
1 parent ec4000d commit cddbe3f

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

.apigentools-info

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2025-04-08 20:55:42.262152",
8-
"spec_repo_commit": "21cf6edb"
7+
"regenerated": "2025-04-09 17:36:48.108017",
8+
"spec_repo_commit": "588d685e"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2025-04-08 20:55:42.277778",
13-
"spec_repo_commit": "21cf6edb"
12+
"regenerated": "2025-04-09 17:36:48.123431",
13+
"spec_repo_commit": "588d685e"
1414
}
1515
}
1616
}

examples/v2/incidents/CreateIncidentType.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
attributes: DatadogAPIClient::V2::IncidentTypeAttributes.new({
1212
description: "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.",
1313
is_default: false,
14-
name: "Security Incident",
14+
name: "Example-Incident",
1515
}),
1616
type: DatadogAPIClient::V2::IncidentTypeType::INCIDENT_TYPES,
1717
}),

features/v2/given.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@
196196
"parameters": [
197197
{
198198
"name": "body",
199-
"value": "{\n \"data\": {\n \"attributes\": {\n \"name\": \"Security Incident\",\n \"description\": \"Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.\",\n \"is_default\": false\n },\n \"type\": \"incident_types\"\n }\n}"
199+
"value": "{\n \"data\": {\n \"attributes\": {\n \"name\": \"{{ unique }}\",\n \"description\": \"Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.\",\n \"is_default\": false\n },\n \"type\": \"incident_types\"\n }\n}"
200200
}
201201
],
202202
"step": "there is a valid \"incident_type\" in the system",

features/v2/incidents.feature

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Feature: Incidents
134134
Scenario: Create an incident type returns "CREATED" response
135135
Given operation "CreateIncidentType" enabled
136136
And new "CreateIncidentType" request
137-
And body with value {"data": {"attributes": {"description": "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.", "is_default": false, "name": "Security Incident"}, "type": "incident_types"}}
137+
And body with value {"data": {"attributes": {"description": "Any incidents that harm (or have the potential to) the confidentiality, integrity, or availability of our data.", "is_default": false, "name": "{{ unique }}"}, "type": "incident_types"}}
138138
When the request is sent
139139
Then the response status is 201 CREATED
140140

0 commit comments

Comments
 (0)