@@ -9,14 +9,14 @@ Feature: On-Call
9
9
And a valid "appKeyAuth" key in the system
10
10
And an instance of "On-Call" API
11
11
12
- @generated @skip @team:DataDog/bugle
12
+ @generated @skip @team:DataDog/on-call
13
13
Scenario : Create On-Call escalation policy returns "Bad Request" response
14
14
Given new "CreateOnCallEscalationPolicy" request
15
15
And body with value {"data" : {"attributes" : {"name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : true, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }, {"id" : "00000000-aba3-0000-0000-000000000000" , "type" : "teams" }]}, {"assignment" : "round-robin" , "escalate_after_seconds" : 3600, "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-abb1-0000-0000-000000000000" , "type" : "users" }]}]}, "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
16
16
When the request is sent
17
17
Then the response status is 400 Bad Request
18
18
19
- @team:DataDog/bugle
19
+ @team:DataDog/on-call
20
20
Scenario : Create On-Call escalation policy returns "Created" response
21
21
Given new "CreateOnCallEscalationPolicy" request
22
22
And there is a valid "user" in the system
@@ -27,14 +27,14 @@ Feature: On-Call
27
27
When the request is sent
28
28
Then the response status is 201 Created
29
29
30
- @generated @skip @team:DataDog/bugle
30
+ @generated @skip @team:DataDog/on-call
31
31
Scenario : Create On-Call schedule returns "Bad Request" response
32
32
Given new "CreateOnCallSchedule" request
33
33
And body with value {"data" : {"attributes" : {"layers" : [{"effective_date" : "2025-02-03T05:00:00Z" , "end_date" : "2025-12-31T00:00:00Z" , "interval" : {"days" : 1}, "members" : [{"user" : {"id" : "00000000-aba1-0000-0000-000000000000" }}], "name" : "Layer 1" , "restrictions" : [{"end_day" : "friday" , "end_time" : "17:00:00" , "start_day" : "monday" , "start_time" : "09:00:00" }], "rotation_start" : "2025-02-01T00:00:00Z" }], "name" : "On-Call Schedule" , "time_zone" : "America/New_York" }, "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "schedules" }}
34
34
When the request is sent
35
35
Then the response status is 400 Bad Request
36
36
37
- @team:DataDog/bugle
37
+ @team:DataDog/on-call
38
38
Scenario : Create On-Call schedule returns "Created" response
39
39
Given new "CreateOnCallSchedule" request
40
40
And there is a valid "user" in the system
@@ -43,7 +43,7 @@ Feature: On-Call
43
43
When the request is sent
44
44
Then the response status is 201 Created
45
45
46
- @team:DataDog/bugle
46
+ @team:DataDog/on-call
47
47
Scenario : Delete On-Call escalation policy returns "No Content" response
48
48
Given new "DeleteOnCallEscalationPolicy" request
49
49
And there is a valid "user" in the system
@@ -54,14 +54,14 @@ Feature: On-Call
54
54
When the request is sent
55
55
Then the response status is 204 No Content
56
56
57
- @generated @skip @team:DataDog/bugle
57
+ @generated @skip @team:DataDog/on-call
58
58
Scenario : Delete On-Call escalation policy returns "Not Found" response
59
59
Given new "DeleteOnCallEscalationPolicy" request
60
60
And request contains "policy_id" parameter from "REPLACE.ME"
61
61
When the request is sent
62
62
Then the response status is 404 Not Found
63
63
64
- @team:DataDog/bugle
64
+ @team:DataDog/on-call
65
65
Scenario : Delete On-Call schedule returns "No Content" response
66
66
Given new "DeleteOnCallSchedule" request
67
67
And there is a valid "user" in the system
@@ -70,28 +70,28 @@ Feature: On-Call
70
70
When the request is sent
71
71
Then the response status is 204 No Content
72
72
73
- @generated @skip @team:DataDog/bugle
73
+ @generated @skip @team:DataDog/on-call
74
74
Scenario : Delete On-Call schedule returns "Not Found" response
75
75
Given new "DeleteOnCallSchedule" request
76
76
And request contains "schedule_id" parameter from "REPLACE.ME"
77
77
When the request is sent
78
78
Then the response status is 404 Not Found
79
79
80
- @generated @skip @team:DataDog/bugle
80
+ @generated @skip @team:DataDog/on-call
81
81
Scenario : Get On-Call escalation policy returns "Bad Request" response
82
82
Given new "GetOnCallEscalationPolicy" request
83
83
And request contains "policy_id" parameter from "REPLACE.ME"
84
84
When the request is sent
85
85
Then the response status is 400 Bad Request
86
86
87
- @generated @skip @team:DataDog/bugle
87
+ @generated @skip @team:DataDog/on-call
88
88
Scenario : Get On-Call escalation policy returns "Not Found" response
89
89
Given new "GetOnCallEscalationPolicy" request
90
90
And request contains "policy_id" parameter from "REPLACE.ME"
91
91
When the request is sent
92
92
Then the response status is 404 Not Found
93
93
94
- @team:DataDog/bugle
94
+ @team:DataDog/on-call
95
95
Scenario : Get On-Call escalation policy returns "OK" response
96
96
Given new "GetOnCallEscalationPolicy" request
97
97
And there is a valid "user" in the system
@@ -103,14 +103,14 @@ Feature: On-Call
103
103
When the request is sent
104
104
Then the response status is 200 OK
105
105
106
- @generated @skip @team:DataDog/bugle
106
+ @generated @skip @team:DataDog/on-call
107
107
Scenario : Get On-Call schedule returns "Not Found" response
108
108
Given new "GetOnCallSchedule" request
109
109
And request contains "schedule_id" parameter from "REPLACE.ME"
110
110
When the request is sent
111
111
Then the response status is 404 Not Found
112
112
113
- @team:DataDog/bugle
113
+ @team:DataDog/on-call
114
114
Scenario : Get On-Call schedule returns "OK" response
115
115
Given new "GetOnCallSchedule" request
116
116
And there is a valid "user" in the system
@@ -119,28 +119,28 @@ Feature: On-Call
119
119
When the request is sent
120
120
Then the response status is 200 OK
121
121
122
- @generated @skip @team:DataDog/bugle
122
+ @generated @skip @team:DataDog/on-call
123
123
Scenario : Get On-Call team routing rules returns "OK" response
124
124
Given new "GetOnCallTeamRoutingRules" request
125
125
And request contains "team_id" parameter from "REPLACE.ME"
126
126
When the request is sent
127
127
Then the response status is 200 OK
128
128
129
- @generated @skip @team:DataDog/bugle
129
+ @generated @skip @team:DataDog/on-call
130
130
Scenario : Get team on-call users returns "Bad Request" response
131
131
Given new "GetTeamOnCallUsers" request
132
132
And request contains "team_id" parameter from "REPLACE.ME"
133
133
When the request is sent
134
134
Then the response status is 400 Bad Request
135
135
136
- @generated @skip @team:DataDog/bugle
136
+ @generated @skip @team:DataDog/on-call
137
137
Scenario : Get team on-call users returns "Not Found" response
138
138
Given new "GetTeamOnCallUsers" request
139
139
And request contains "team_id" parameter from "REPLACE.ME"
140
140
When the request is sent
141
141
Then the response status is 404 Not Found
142
142
143
- @team:DataDog/bugle
143
+ @team:DataDog/on-call
144
144
Scenario : Get team on-call users returns "OK" response
145
145
Given new "GetTeamOnCallUsers" request
146
146
And there is a valid "user" in the system
@@ -153,21 +153,21 @@ Feature: On-Call
153
153
When the request is sent
154
154
Then the response status is 200 OK
155
155
156
- @generated @skip @team:DataDog/bugle
156
+ @generated @skip @team:DataDog/on-call
157
157
Scenario : Get the schedule on-call user returns "Bad Request" response
158
158
Given new "GetScheduleOnCallUser" request
159
159
And request contains "schedule_id" parameter from "REPLACE.ME"
160
160
When the request is sent
161
161
Then the response status is 400 Bad Request
162
162
163
- @generated @skip @team:DataDog/bugle
163
+ @generated @skip @team:DataDog/on-call
164
164
Scenario : Get the schedule on-call user returns "Not Found" response
165
165
Given new "GetScheduleOnCallUser" request
166
166
And request contains "schedule_id" parameter from "REPLACE.ME"
167
167
When the request is sent
168
168
Then the response status is 404 Not Found
169
169
170
- @team:DataDog/bugle
170
+ @team:DataDog/on-call
171
171
Scenario : Get the schedule on-call user returns "OK" response
172
172
Given new "GetScheduleOnCallUser" request
173
173
And there is a valid "user" in the system
@@ -176,7 +176,7 @@ Feature: On-Call
176
176
When the request is sent
177
177
Then the response status is 200 OK
178
178
179
- @skip-python @team:DataDog/bugle
179
+ @skip-python @team:DataDog/on-call
180
180
Scenario : Set On-Call team routing rules returns "OK" response
181
181
Given new "SetOnCallTeamRoutingRules" request
182
182
And there is a valid "user" in the system
@@ -189,23 +189,23 @@ Feature: On-Call
189
189
When the request is sent
190
190
Then the response status is 200 OK
191
191
192
- @generated @skip @team:DataDog/bugle
192
+ @generated @skip @team:DataDog/on-call
193
193
Scenario : Update On-Call escalation policy returns "Bad Request" response
194
194
Given new "UpdateOnCallEscalationPolicy" request
195
195
And request contains "policy_id" parameter from "REPLACE.ME"
196
196
And body with value {"data" : {"attributes" : {"name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : false, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "id" : "00000000-aba1-0000-0000-000000000000" , "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }]}]}, "id" : "a3000000-0000-0000-0000-000000000000" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
197
197
When the request is sent
198
198
Then the response status is 400 Bad Request
199
199
200
- @generated @skip @team:DataDog/bugle
200
+ @generated @skip @team:DataDog/on-call
201
201
Scenario : Update On-Call escalation policy returns "Not Found" response
202
202
Given new "UpdateOnCallEscalationPolicy" request
203
203
And request contains "policy_id" parameter from "REPLACE.ME"
204
204
And body with value {"data" : {"attributes" : {"name" : "Escalation Policy 1" , "resolve_page_on_policy_end" : false, "retries" : 2, "steps" : [{"assignment" : "default" , "escalate_after_seconds" : 3600, "id" : "00000000-aba1-0000-0000-000000000000" , "targets" : [{"id" : "00000000-aba1-0000-0000-000000000000" , "type" : "users" }, {"id" : "00000000-aba2-0000-0000-000000000000" , "type" : "schedules" }]}]}, "id" : "a3000000-0000-0000-0000-000000000000" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "policies" }}
205
205
When the request is sent
206
206
Then the response status is 404 Not Found
207
207
208
- @team:DataDog/bugle
208
+ @team:DataDog/on-call
209
209
Scenario : Update On-Call escalation policy returns "OK" response
210
210
Given new "UpdateOnCallEscalationPolicy" request
211
211
And there is a valid "user" in the system
@@ -217,23 +217,23 @@ Feature: On-Call
217
217
When the request is sent
218
218
Then the response status is 200 OK
219
219
220
- @generated @skip @team:DataDog/bugle
220
+ @generated @skip @team:DataDog/on-call
221
221
Scenario : Update On-Call schedule returns "Bad Request" response
222
222
Given new "UpdateOnCallSchedule" request
223
223
And request contains "schedule_id" parameter from "REPLACE.ME"
224
224
And body with value {"data" : {"attributes" : {"layers" : [{"effective_date" : "2025-02-03T05:00:00Z" , "end_date" : "2025-12-31T00:00:00Z" , "interval" : {"seconds" : 3600}, "members" : [{"user" : {"id" : "00000000-aba1-0000-0000-000000000000" }}], "name" : "Layer 1" , "restrictions" : [{"end_day" : "friday" , "end_time" : "17:00:00" , "start_day" : "monday" , "start_time" : "09:00:00" }], "rotation_start" : "2025-02-01T00:00:00Z" }], "name" : "On-Call Schedule Updated" , "time_zone" : "America/New_York" }, "id" : "3653d3c6-0c75-11ea-ad28-fb5701eabc7d" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "schedules" }}
225
225
When the request is sent
226
226
Then the response status is 400 Bad Request
227
227
228
- @generated @skip @team:DataDog/bugle
228
+ @generated @skip @team:DataDog/on-call
229
229
Scenario : Update On-Call schedule returns "Not Found" response
230
230
Given new "UpdateOnCallSchedule" request
231
231
And request contains "schedule_id" parameter from "REPLACE.ME"
232
232
And body with value {"data" : {"attributes" : {"layers" : [{"effective_date" : "2025-02-03T05:00:00Z" , "end_date" : "2025-12-31T00:00:00Z" , "interval" : {"seconds" : 3600}, "members" : [{"user" : {"id" : "00000000-aba1-0000-0000-000000000000" }}], "name" : "Layer 1" , "restrictions" : [{"end_day" : "friday" , "end_time" : "17:00:00" , "start_day" : "monday" , "start_time" : "09:00:00" }], "rotation_start" : "2025-02-01T00:00:00Z" }], "name" : "On-Call Schedule Updated" , "time_zone" : "America/New_York" }, "id" : "3653d3c6-0c75-11ea-ad28-fb5701eabc7d" , "relationships" : {"teams" : {"data" : [{"id" : "00000000-da3a-0000-0000-000000000000" , "type" : "teams" }]}}, "type" : "schedules" }}
233
233
When the request is sent
234
234
Then the response status is 404 Not Found
235
235
236
- @team:DataDog/bugle
236
+ @team:DataDog/on-call
237
237
Scenario : Update On-Call schedule returns "OK" response
238
238
Given new "UpdateOnCallSchedule" request
239
239
And there is a valid "user" in the system
0 commit comments