-
Notifications
You must be signed in to change notification settings - Fork 20
Expand file tree
/
Copy pathroles.feature
More file actions
340 lines (303 loc) · 16.6 KB
/
roles.feature
File metadata and controls
340 lines (303 loc) · 16.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
@endpoint(roles) @endpoint(roles-v2)
Feature: Roles
The Roles API is used to create and manage Datadog roles, what [global
permissions](https://docs.datadoghq.com/account_management/rbac/) they
grant, and which users belong to them. Permissions related to specific
account assets can be granted to roles in the Datadog application without
using this API. For example, granting read access on a specific log index
to a role can be done in Datadog from the [Pipelines
page](https://app.datadoghq.com/logs/pipelines).
Background:
Given a valid "apiKeyAuth" key in the system
And a valid "appKeyAuth" key in the system
And an instance of "Roles" API
@generated @skip @team:DataDog/aaa-core-access
Scenario: Add a user to a role returns "Bad Request" response
Given new "AddUserToRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "00000000-0000-0000-2345-000000000000", "type": "users"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/aaa-core-access
Scenario: Add a user to a role returns "Not found" response
Given new "AddUserToRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "00000000-0000-0000-2345-000000000000", "type": "users"}}
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Add a user to a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "user" in the system
And new "AddUserToRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ user.data.id}}", "type": "{{ user.data.type }}"}}
When the request is sent
Then the response status is 200 OK
And the response "data[0].id" is equal to "{{ user.data.id }}"
And the response "data[0].type" is equal to "{{ user.data.type }}"
And the response "data[0].relationships.roles.data" has item with field "id" with value "{{ role.data.id }}"
@team:DataDog/aaa-core-access
Scenario: Create a new role by cloning an existing role returns "Bad Request" response
Given there is a valid "role" in the system
And new "CloneRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"attributes": {"name": " "}, "type": "roles"}}
When the request is sent
Then the response status is 400 Bad Request
@team:DataDog/aaa-core-access
Scenario: Create a new role by cloning an existing role returns "Conflict" response
Given there is a valid "role" in the system
And new "CloneRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"attributes": {"name": "{{ role.data.attributes.name }}"}, "type": "roles"}}
When the request is sent
Then the response status is 409 Conflict
@generated @skip @team:DataDog/aaa-core-access
Scenario: Create a new role by cloning an existing role returns "Not found" response
Given new "CloneRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"name": "cloned-role"}, "type": "roles"}}
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Create a new role by cloning an existing role returns "OK" response
Given there is a valid "role" in the system
And new "CloneRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"attributes": {"name": "{{ unique }} clone"}, "type": "roles"}}
When the request is sent
Then the response status is 200 OK
And the response "data.attributes.name" is equal to "{{ unique }} clone"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Create role returns "Bad Request" response
Given new "CreateRole" request
And body with value {"data": {"attributes": {"name": "developers"}, "relationships": {"permissions": {"data": [{"type": "permissions"}]}}, "type": "roles"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/aaa-core-access
Scenario: Create role returns "OK" response
Given new "CreateRole" request
And body with value {"data": {"attributes": {"name": "developers"}, "relationships": {"permissions": {"data": [{"type": "permissions"}]}}, "type": "roles"}}
When the request is sent
Then the response status is 200 OK
@team:DataDog/aaa-core-access
Scenario: Create role with a permission returns "OK" response
Given new "CreateRole" request
And there is a valid "permission" in the system
And body with value {"data": {"type": "roles", "attributes": {"name": "{{ unique }}"}, "relationships": {"permissions": {"data": [{"id": "{{ permission.id }}", "type": "{{ permission.type }}"}]}}}}
When the request is sent
Then the response status is 200 OK
And the response "data.attributes.name" is equal to "{{ unique }}"
And the response "data.type" is equal to "roles"
And the response "data.relationships.permissions.data" has item with field "id" with value "{{ permission.id }}"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Delete role returns "Not found" response
Given new "DeleteRole" request
And request contains "role_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Delete role returns "OK" response
Given there is a valid "role" in the system
And new "DeleteRole" request
And request contains "role_id" parameter from "role.data.id"
When the request is sent
Then the response status is 204 OK
@generated @skip @team:DataDog/aaa-core-access
Scenario: Get a role returns "Not found" response
Given new "GetRole" request
And request contains "role_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Get a role returns "OK" response
Given there is a valid "role" in the system
And new "GetRole" request
And request contains "role_id" parameter from "role.data.id"
When the request is sent
Then the response status is 200 OK for get role
And the response "data.attributes.name" has the same value as "role.data.attributes.name"
And the response "data.id" has the same value as "role.data.id"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Get all users of a role returns "Not found" response
Given new "ListRoleUsers" request
And request contains "role_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Get all users of a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "user" in the system
And the "user" has the "role"
And new "ListRoleUsers" request
And request contains "role_id" parameter from "role.data.id"
When the request is sent
Then the response status is 200 OK
And the response "meta.page.total_count" is equal to 1
And the response "data" has item with field "id" with value "{{ user.data.id }}"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Grant permission to a role returns "Bad Request" response
Given new "AddPermissionToRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"type": "permissions"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/aaa-core-access
Scenario: Grant permission to a role returns "Not found" response
Given new "AddPermissionToRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"type": "permissions"}}
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Grant permission to a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And new "AddPermissionToRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ permission.id }}", "type": "{{ permission.type }}"}}
When the request is sent
Then the response status is 200 OK
And the response "data[0].type" is equal to "{{ permission.type }}"
And the response "data" has item with field "id" with value "{{ permission.id }}"
@generated @skip @team:DataDog/aaa-core-access
Scenario: List permissions for a role returns "Not found" response
Given new "ListRolePermissions" request
And request contains "role_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: List permissions for a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And the "permission" is granted to the "role"
And new "ListRolePermissions" request
And request contains "role_id" parameter from "role.data.id"
When the request is sent
Then the response status is 200 OK
And the response "data[0].type" is equal to "{{ permission.type }}"
And the response "data" has item with field "id" with value "{{ permission.id }}"
@generated @skip @team:DataDog/aaa-core-access
Scenario: List permissions returns "Bad Request" response
Given new "ListPermissions" request
When the request is sent
Then the response status is 400 Bad Request
@team:DataDog/aaa-core-access
Scenario: List permissions returns "OK" response
Given new "ListPermissions" request
When the request is sent
Then the response status is 200 OK
And the response "data" has item with field "attributes.restricted" with value true
And the response "data" has item with field "attributes.restricted" with value false
And the response "data" has item with field "attributes.name" with value "admin"
@generated @skip @team:DataDog/aaa-core-access
Scenario: List role templates returns "OK" response
Given operation "ListRoleTemplates" enabled
And new "ListRoleTemplates" request
When the request is sent
Then the response status is 200 OK
@team:DataDog/aaa-core-access
Scenario: List roles returns "OK" response
Given there is a valid "role" in the system
And new "ListRoles" request
And request contains "filter" parameter from "role.data.attributes.name"
When the request is sent
Then the response status is 200 OK
And the response "meta.page.total_filtered_count" is equal to 1
And the response "data[0].id" has the same value as "role.data.id"
And the response "data[0].attributes.name" has the same value as "role.data.attributes.name"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Remove a user from a role returns "Bad Request" response
Given new "RemoveUserFromRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "00000000-0000-0000-2345-000000000000", "type": "users"}}
When the request is sent
Then the response status is 400 Bad Request
@generated @skip @team:DataDog/aaa-core-access
Scenario: Remove a user from a role returns "Not found" response
Given new "RemoveUserFromRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"id": "00000000-0000-0000-2345-000000000000", "type": "users"}}
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Remove a user from a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "user" in the system
And the "user" has the "role"
And new "RemoveUserFromRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ user.data.id}}", "type": "{{ user.data.type }}"}}
When the request is sent
Then the response status is 200 OK
@skip-validation @team:DataDog/aaa-core-access
Scenario: Revoke permission returns "Bad Request" response
Given there is a valid "role" in the system
And new "RemovePermissionFromRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "11111111-dead-beef-dead-ffffffffffff", "type": "bad_permission_type"}}
When the request is sent
Then the response status is 400 Bad Request
@team:DataDog/aaa-core-access
Scenario: Revoke permission returns "Not found" response
Given there is a valid "permission" in the system
And new "RemovePermissionFromRole" request
And request contains "role_id" parameter with value "00000000-dead-beef-dead-ffffffffffff"
And body with value {"data": {"id": "{{ permission.id }}", "type": "{{ permission.type }}"}}
When the request is sent
Then the response status is 404 Not found
@team:DataDog/aaa-core-access
Scenario: Revoke permission returns "OK" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And the "permission" is granted to the "role"
And new "RemovePermissionFromRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ permission.id }}", "type": "{{ permission.type }}"}}
When the request is sent
Then the response status is 200 OK
And the response "data[0].type" is equal to "permissions"
@team:DataDog/aaa-core-access
Scenario: Update a role returns "Bad Request" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And new "UpdateRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ role.data.id }}", "type": "roles", "attributes": {"name" : "{{ role.data.attributes.name }}-updated"}, "relationships": {"permissions": {"data": [{"id": "11111111-dead-beef-dead-ffffffffffff", "type": "{{ permission.type }}"}]}}}}
When the request is sent
Then the response status is 400 Bad Request
@team:DataDog/aaa-core-access
Scenario: Update a role returns "Bad Role ID" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And new "UpdateRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "00000000-dead-beef-dead-ffffffffffff", "type": "roles", "attributes": {"name" : "{{ role.data.attributes.name }}-updated"}, "relationships": {"permissions": {"data": [{"type": "{{ permission.type }}", "id": "{{ permission.id }}"}]}}}}
When the request is sent
Then the response status is 422 Bad Role ID in Request
@team:DataDog/aaa-core-access
Scenario: Update a role returns "Not found" response
Given there is a valid "permission" in the system
And new "UpdateRole" request
And request contains "role_id" parameter with value "00000000-dead-beef-dead-ffffffffffff"
And body with value {"data": {"id": "00000000-dead-beef-dead-ffffffffffff", "type": "roles", "attributes": {"name" : "updated"}, "relationships": {"permissions": {"data": [{"type": "{{ permission.type }}", "id": "{{ permission.id }}"}]}}}}
When the request is sent
Then the response status is 404 Not found
@skip @team:DataDog/aaa-core-access
Scenario: Update a role returns "OK" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And new "UpdateRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "{{ role.data.id }}", "type": "roles", "attributes": {"name" : "{{ role.data.attributes.name }}-updated"}, "relationships": {"permissions": {"data": [{"id": "{{ permission.id }}", "type": "{{ permission.type }}"}]}}}}
When the request is sent
Then the response status is 200 OK
And the response "data.attributes.name" is equal to "{{ role.data.attributes.name }}-updated"
@generated @skip @team:DataDog/aaa-core-access
Scenario: Update a role returns "Unprocessable Entity" response
Given new "UpdateRole" request
And request contains "role_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {}, "id": "00000000-0000-1111-0000-000000000000", "relationships": {"permissions": {"data": [{"type": "permissions"}]}}, "type": "roles"}}
When the request is sent
Then the response status is 422 Unprocessable Entity