Regenerate client from commit 5860386 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -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
@@ -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

examples/v2/on-call/GetScheduleOnCallUser.java

@@ -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;

src/main/java/com/datadog/api/client/v2/api/OnCallApi.java

@@ -1358,7 +1358,7 @@ public GetScheduleOnCallUserOptionalParameters filterAtTs(String filterAtTs) {
   }
 
   /**
-   * Get the schedule on-call user.
+   * Get scheduled on-call user.
    *
    * <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
    *
@@ -1373,7 +1373,7 @@ scheduleId, new GetScheduleOnCallUserOptionalParameters())
   }
 
   /**
-   * Get the schedule on-call user.
+   * Get scheduled on-call user.
    *
    * <p>See {@link #getScheduleOnCallUserWithHttpInfoAsync}.
    *
@@ -1390,7 +1390,7 @@ scheduleId, new GetScheduleOnCallUserOptionalParameters())
   }
 
   /**
-   * Get the schedule on-call user.
+   * Get scheduled on-call user.
    *
    * <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
    *
@@ -1405,7 +1405,7 @@ public Shift getScheduleOnCallUser(
   }
 
   /**
-   * Get the schedule on-call user.
+   * Get scheduled on-call user.
    *
    * <p>See {@link #getScheduleOnCallUserWithHttpInfoAsync}.
    *
@@ -1485,7 +1485,7 @@ public ApiResponse<Shift> getScheduleOnCallUserWithHttpInfo(
   }
 
   /**
-   * Get the schedule on-call user.
+   * Get scheduled on-call user.
    *
    * <p>See {@link #getScheduleOnCallUserWithHttpInfo}.
    *

src/test/resources/cassettes/features/v2/Get_the_schedule_on_call_user_returns_OK_response.freeze

@@ -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