Skip to content

Commit 25a4089

Browse files
api-clients-generation-pipeline[bot]ci.datadog-api-spec
api-clients-generation-pipeline[bot]
and
ci.datadog-api-spec
authored
Regenerate client from commit ea548b1 of spec repo (#182)
Co-authored-by: ci.datadog-api-spec <[email protected]>
1 parent ab34885 commit 25a4089

File tree

3 files changed

+161
-16
lines changed

3 files changed

+161
-16
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.3.0",
7-
"regenerated": "2020-12-02 08:54:23.344270",
8-
"spec_repo_commit": "cdc8c0b"
7+
"regenerated": "2020-12-07 17:47:05.841868",
8+
"spec_repo_commit": "ea548b1"
99
},
1010
"v2": {
1111
"apigentools_version": "1.3.0",
12-
"regenerated": "2020-12-02 08:54:33.564570",
13-
"spec_repo_commit": "cdc8c0b"
12+
"regenerated": "2020-12-07 17:47:15.963438",
13+
"spec_repo_commit": "ea548b1"
1414
}
1515
}
1616
}

‎tests/v2/features/key_management.feature

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
@endpoint(key-management)
2+
Feature: Key Management
3+
Manage your Datadog API and application keys. You need an API and
4+
applications key with Admin rights to interact with this endpoint. The
5+
full list of keys can be seen on your [Datadog API
6+
page](https://app.datadoghq.com/account/settings#api).
7+
8+
Background:
9+
Given a valid "apiKeyAuth" key in the system
10+
And a valid "appKeyAuth" key in the system
11+
And an instance of "KeyManagement" API
12+
13+
@skip
14+
Scenario: Get all Application keys returns "OK" response
15+
Given new "ListApplicationKeys" request
16+
When the request is sent
17+
Then the response status is 200 OK
18+
19+
@skip
20+
Scenario: Delete an Application key returns "No Content" response
21+
Given there is a valid "application_key" in the system
22+
And new "DeleteApplicationKey" request
23+
And request contains "app_key_id" parameter from "application_key.data.id"
24+
When the request is sent
25+
Then the response status is 204 No Content
26+
27+
@skip
28+
Scenario: Get all Application keys owned by current user returns "OK" response
29+
Given new "ListCurrentUserApplicationKeys" request
30+
When the request is sent
31+
Then the response status is 200 OK
32+
33+
@skip
34+
Scenario: Create an Application key for current user returns "Created" response
35+
Given new "CreateCurrentUserApplicationKey" request
36+
And body {"data": {"type": "application_keys", "attributes": {"name": "{{ unique }}"}}}
37+
When the request is sent
38+
Then the response status is 201 Created
39+
And the response "data.attributes.name" is equal to "{{ unique }}"
40+
41+
@skip
42+
Scenario: Delete an Application key owned by current user returns "No Content" response
43+
Given there is a valid "application_key" in the system
44+
And new "DeleteCurrentUserApplicationKey" request
45+
And request contains "app_key_id" parameter from "application_key.data.id"
46+
When the request is sent
47+
Then the response status is 204 No Content
48+
49+
@skip
50+
Scenario: Get one Application key owned by current user returns "OK" response
51+
Given there is a valid "application_key" in the system
52+
And new "GetCurrentUserApplicationKey" request
53+
And request contains "app_key_id" parameter from "application_key.data.id"
54+
When the request is sent
55+
Then the response status is 200 OK
56+
And the response "data.attributes.name" has the same value as "application_key.data.attributes.name"
57+
58+
@skip
59+
Scenario: Edit an application key owned by current user returns "OK" response
60+
Given there is a valid "application_key" in the system
61+
And new "UpdateCurrentUserApplicationKey" request
62+
And request contains "app_key_id" parameter from "application_key.data.id"
63+
And body {"data": {"id": "{{ application_key.data.id }}", "type": "application_keys", "attributes": {"name" : "{{ application_key.data.attributes.name }}-updated"}}}
64+
When the request is sent
65+
Then the response status is 200 OK
66+
And the response "data.attributes.name" is equal to "{{ application_key.data.attributes.name }}-updated"
67+
68+
@skip
69+
Scenario: Edit an application key returns "OK" response
70+
Given there is a valid "application_key" in the system
71+
And new "UpdateApplicationKey" request
72+
And request contains "app_key_id" parameter from "application_key.data.id"
73+
And body {"data": {"id": "{{ application_key.data.id }}", "type": "application_keys", "attributes": {"name" : "{{ application_key.data.attributes.name }}-updated"}}}
74+
When the request is sent
75+
Then the response status is 200 OK
76+
And the response "data.attributes.name" is equal to "{{ application_key.data.attributes.name }}-updated"
77+
78+
@generated @skip
79+
Scenario: Get all application keys returns "OK" response
80+
Given new "ListApplicationKeys" request
81+
When the request is sent
82+
Then the response status is 200 OK
83+
84+
@generated @skip
85+
Scenario: Delete an application key returns "No Content" response
86+
Given new "DeleteApplicationKey" request
87+
And request contains "app_key_id" parameter from "<PATH>"
88+
When the request is sent
89+
Then the response status is 204 No Content

‎tests/v2/features/undo.json

Lines changed: 68 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,59 @@
11
{
2+
"ListApplicationKeys": {
3+
"tag": "Key Management",
4+
"undo": {
5+
"type": "safe"
6+
}
7+
},
8+
"DeleteApplicationKey": {
9+
"tag": "Key Management",
10+
"undo": {
11+
"type": "idempotent"
12+
}
13+
},
14+
"UpdateApplicationKey": {
15+
"tag": "Key Management",
16+
"undo": {
17+
"type": "idempotent"
18+
}
19+
},
20+
"ListCurrentUserApplicationKeys": {
21+
"tag": "Key Management",
22+
"undo": {
23+
"type": "safe"
24+
}
25+
},
26+
"CreateCurrentUserApplicationKey": {
27+
"tag": "Key Management",
28+
"undo": {
29+
"operationId": "DeleteCurrentUserApplicationKey",
30+
"parameters": [
31+
{
32+
"name": "app_key_id",
33+
"source": "data.id"
34+
}
35+
],
36+
"type": "unsafe"
37+
}
38+
},
39+
"DeleteCurrentUserApplicationKey": {
40+
"tag": "Key Management",
41+
"undo": {
42+
"type": "idempotent"
43+
}
44+
},
45+
"GetCurrentUserApplicationKey": {
46+
"tag": "Key Management",
47+
"undo": {
48+
"type": "safe"
49+
}
50+
},
51+
"UpdateCurrentUserApplicationKey": {
52+
"tag": "Key Management",
53+
"undo": {
54+
"type": "idempotent"
55+
}
56+
},
257
"DeleteDashboardListItems": {
358
"tag": "Dashboard Lists",
459
"undo": {
@@ -14,19 +69,14 @@
1469
"CreateDashboardListItems": {
1570
"tag": "Dashboard Lists",
1671
"undo": {
17-
"operationId": "DeleteDashboardListItems",
18-
"parameters": [
19-
{
20-
"name": "dashboard_list_id",
21-
"source": "<RESPONSE_PATH>"
22-
}
23-
],
24-
"type": "unsafe"
72+
"type": "safe"
2573
}
2674
},
2775
"UpdateDashboardListItems": {
2876
"tag": "Dashboard Lists",
29-
"undo": null
77+
"undo": {
78+
"type": "safe"
79+
}
3080
},
3181
"ListIncidents": {
3282
"tag": "Incidents",
@@ -79,7 +129,9 @@
79129
},
80130
"UpdateLogsArchiveOrder": {
81131
"tag": "Logs Archives",
82-
"undo": null
132+
"undo": {
133+
"type": "safe"
134+
}
83135
},
84136
"ListLogsArchives": {
85137
"tag": "Logs Archives",
@@ -114,7 +166,9 @@
114166
},
115167
"UpdateLogsArchive": {
116168
"tag": "Logs Archives",
117-
"undo": null
169+
"undo": {
170+
"type": "safe"
171+
}
118172
},
119173
"RemoveRoleFromArchive": {
120174
"tag": "Logs Archives",
@@ -130,7 +184,9 @@
130184
},
131185
"AddReadRoleToArchive": {
132186
"tag": "Logs Archives",
133-
"undo": null
187+
"undo": {
188+
"type": "unsafe"
189+
}
134190
},
135191
"ListLogsGet": {
136192
"tag": "Logs",

0 commit comments

Comments
 (0)