Skip to content

Add permission requirements to on-call endpoints #3286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
api-clients-generation-pipeline wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add permission requirements to on-call endpoints #3286

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74529,9 +74529,13 @@ paths:
- apiKeyAuth: []
appKeyAuth: []
- AuthZ: []
summary: Get the schedule on-call user
summary: Get scheduled on-call user
tags:
- On-Call
x-permission:
operator: AND
permissions:
- on_call_read
/api/v2/on-call/teams/{team_id}/on-call:
get:
description: Get a team's on-call users at a given time
Expand Down Expand Up @@ -74574,6 +74578,10 @@ paths:
summary: Get team on-call users
tags:
- On-Call
x-permission:
operator: AND
permissions:
- on_call_read
/api/v2/on-call/teams/{team_id}/routing-rules:
get:
description: Get a team's On-Call routing rules
Expand Down
2 changes: 1 addition & 1 deletion examples/v2/on-call/GetScheduleOnCallUser.java
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
// Get the schedule on-call user returns "OK" response
// Get scheduled on-call user returns "OK" response

import com.datadog.api.client.ApiClient;
import com.datadog.api.client.ApiException;
Expand Down
10 changes: 5 additions & 5 deletions src/main/java/com/datadog/api/client/v2/api/OnCallApi.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1358,7 +1358,7 @@ public GetScheduleOnCallUserOptionalParameters filterAtTs(String filterAtTs) {
}

/**
* Get the schedule on-call user.
* Get scheduled on-call user.
*
* <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
*
Expand All @@ -1373,7 +1373,7 @@ scheduleId, new GetScheduleOnCallUserOptionalParameters())
}

/**
* Get the schedule on-call user.
* Get scheduled on-call user.
*
* <p>See {@link #getScheduleOnCallUserWithHttpInfoAsync}.
*
Expand All @@ -1390,7 +1390,7 @@ scheduleId, new GetScheduleOnCallUserOptionalParameters())
}

/**
* Get the schedule on-call user.
* Get scheduled on-call user.
*
* <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
*
Expand All @@ -1405,7 +1405,7 @@ public Shift getScheduleOnCallUser(
}

/**
* Get the schedule on-call user.
* Get scheduled on-call user.
*
* <p>See {@link #getScheduleOnCallUserWithHttpInfoAsync}.
*
Expand Down Expand Up @@ -1485,7 +1485,7 @@ public ApiResponse<Shift> getScheduleOnCallUserWithHttpInfo(
}

/**
* Get the schedule on-call user.
* Get scheduled on-call user.
*
* <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
*
Expand Down
1 change: 0 additions & 1 deletion .../resources/cassettes/features/v2/Get_the_schedule_on_call_user_returns_OK_response.freeze
View file
Open in desktop

This file was deleted.

130 changes: 0 additions & 130 deletions ...st/resources/cassettes/features/v2/Get_the_schedule_on_call_user_returns_OK_response.json
View file
Open in desktop

This file was deleted.

44 changes: 22 additions & 22 deletions src/test/resources/com/datadog/api/client/v2/api/on-call.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,52 +127,52 @@ Feature: On-Call
Then the response status is 200 OK

@generated @skip @team:DataDog/on-call
Scenario: Get team on-call users returns "Bad Request" response
Given new "GetTeamOnCallUsers" request
And request contains "team_id" parameter from "REPLACE.ME"
Scenario: Get scheduled on-call user returns "Bad Request" response
Given new "GetScheduleOnCallUser" request
And request contains "schedule_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/on-call
Scenario: Get team on-call users returns "Not Found" response
Given new "GetTeamOnCallUsers" request
And request contains "team_id" parameter from "REPLACE.ME"
Scenario: Get scheduled on-call user returns "Not Found" response
Given new "GetScheduleOnCallUser" request
And request contains "schedule_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/on-call
Scenario: Get team on-call users returns "OK" response
Given new "GetTeamOnCallUsers" request
Scenario: Get scheduled on-call user returns "OK" response
Given new "GetScheduleOnCallUser" request
And there is a valid "user" in the system
And there is a valid "dd_team" in the system
And there is a valid "schedule" in the system
And there is a valid "escalation_policy" in the system
And there are valid "routing_rules" in the system
And request contains "team_id" parameter from "routing_rules.data.id"
And request contains "include" parameter with value "responders,escalations.responders"
And request contains "schedule_id" parameter from "schedule.data.id"
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/on-call
Scenario: Get the schedule on-call user returns "Bad Request" response
Given new "GetScheduleOnCallUser" request
And request contains "schedule_id" parameter from "REPLACE.ME"
Scenario: Get team on-call users returns "Bad Request" response
Given new "GetTeamOnCallUsers" request
And request contains "team_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/on-call
Scenario: Get the schedule on-call user returns "Not Found" response
Given new "GetScheduleOnCallUser" request
And request contains "schedule_id" parameter from "REPLACE.ME"
Scenario: Get team on-call users returns "Not Found" response
Given new "GetTeamOnCallUsers" request
And request contains "team_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/on-call
Scenario: Get the schedule on-call user returns "OK" response
Given new "GetScheduleOnCallUser" request
Scenario: Get team on-call users returns "OK" response
Given new "GetTeamOnCallUsers" request
And there is a valid "user" in the system
And there is a valid "dd_team" in the system
And there is a valid "schedule" in the system
And request contains "schedule_id" parameter from "schedule.data.id"
And there is a valid "escalation_policy" in the system
And there are valid "routing_rules" in the system
And request contains "team_id" parameter from "routing_rules.data.id"
And request contains "include" parameter with value "responders,escalations.responders"
When the request is sent
Then the response status is 200 OK

Expand Down
Loading