Skip to content

Commit bf453b1

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 8a099df of spec repo
1 parent d4302f9 commit bf453b1

File tree

2 files changed

+23
-8
lines changed

2 files changed

+23
-8
lines changed

.generator/schemas/v2/openapi.yaml

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72918,9 +72918,13 @@ paths:
7291872918
- apiKeyAuth: []
7291972919
appKeyAuth: []
7292072920
- AuthZ: []
72921-
summary: Get the schedule on-call user
72921+
summary: Get the scheduled on-call user
7292272922
tags:
7292372923
- On-Call
72924+
x-permission:
72925+
operator: AND
72926+
permissions:
72927+
- on_call_write
7292472928
/api/v2/on-call/teams/{team_id}/on-call:
7292572929
get:
7292672930
description: Get a team's on-call users at a given time
@@ -72963,6 +72967,10 @@ paths:
7296372967
summary: Get team on-call users
7296472968
tags:
7296572969
- On-Call
72970+
x-permission:
72971+
operator: AND
72972+
permissions:
72973+
- on_call_write
7296672974
/api/v2/on-call/teams/{team_id}/routing-rules:
7296772975
get:
7296872976
description: Get a team's On-Call routing rules

features/v2/on-call.feature

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -153,26 +153,33 @@ Feature: On-Call
153153
When the request is sent
154154
Then the response status is 200 OK
155155

156+
@team:DataDog/on-call
157+
Scenario: Get the schedule on-call user returns "OK" response
158+
Given new "GetScheduleOnCallUser" request
159+
And there is a valid "user" in the system
160+
And there is a valid "schedule" in the system
161+
And request contains "schedule_id" parameter from "schedule.data.id"
162+
When the request is sent
163+
Then the response status is 200 OK
164+
156165
@generated @skip @team:DataDog/on-call
157-
Scenario: Get the schedule on-call user returns "Bad Request" response
166+
Scenario: Get the scheduled on-call user returns "Bad Request" response
158167
Given new "GetScheduleOnCallUser" request
159168
And request contains "schedule_id" parameter from "REPLACE.ME"
160169
When the request is sent
161170
Then the response status is 400 Bad Request
162171

163172
@generated @skip @team:DataDog/on-call
164-
Scenario: Get the schedule on-call user returns "Not Found" response
173+
Scenario: Get the scheduled on-call user returns "Not Found" response
165174
Given new "GetScheduleOnCallUser" request
166175
And request contains "schedule_id" parameter from "REPLACE.ME"
167176
When the request is sent
168177
Then the response status is 404 Not Found
169178

170-
@team:DataDog/on-call
171-
Scenario: Get the schedule on-call user returns "OK" response
179+
@generated @skip @team:DataDog/on-call
180+
Scenario: Get the scheduled on-call user returns "OK" response
172181
Given new "GetScheduleOnCallUser" request
173-
And there is a valid "user" in the system
174-
And there is a valid "schedule" in the system
175-
And request contains "schedule_id" parameter from "schedule.data.id"
182+
And request contains "schedule_id" parameter from "REPLACE.ME"
176183
When the request is sent
177184
Then the response status is 200 OK
178185

0 commit comments

Comments
 (0)