Fix On-Call Paging success status codes

.generator/schemas/v2/openapi.yaml

@@ -26432,15 +26432,15 @@ components:
           description: A short summary of the issue or context.
           type: string
         tags:
-          description: Tags to help categorize or filter the page.
+          description: Tags to help categorize or filter the Page.
           items:
-            description: A single tag for categorizing the page.
+            description: A single tag for categorizing the Page.
             type: string
           type: array
         target:
           $ref: "#/components/schemas/CreatePageRequestDataAttributesTarget"
         title:
-          description: The title of the page.
+          description: The title of the Page.
           example: "Service: Test is down"
           type: string
         urgency:
@@ -26479,10 +26479,10 @@ components:
           $ref: "#/components/schemas/CreatePageResponseData"
       type: object
     CreatePageResponseData:
-      description: The information returned after successfully creating a page.
+      description: The information returned after successfully creating a Page.
       properties:
         id:
-          description: The unique ID of the created page.
+          description: The unique ID of the created Page.
           type: string
         type:
           $ref: "#/components/schemas/CreatePageResponseDataType"
@@ -106350,7 +106350,7 @@ components:
       description: Details about where to reroute the On-Call Page.
       properties:
         comment:
-          description: An optional comment explaining why the page is being rerouted.
+          description: An optional comment explaining why the Page is being rerouted.
           example: Rerouting to the database team.
           type: string
         target:
@@ -208562,7 +208562,7 @@ paths:
               $ref: "#/components/schemas/CreatePageRequest"
         required: true
       responses:
-        "200":
+        "201":
           content:
             application/json:
               examples:
@@ -208573,7 +208573,7 @@ paths:
                       type: pages
               schema:
                 $ref: "#/components/schemas/CreatePageResponse"
-          description: OK.
+          description: Created.
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:
@@ -208765,7 +208765,7 @@ paths:
         Acknowledges an On-Call Page.
       operationId: AcknowledgeOnCallPage
       parameters:
-        - description: The page ID.
+        - description: The Page ID.
           in: path
           name: page_id
           required: true
@@ -208774,8 +208774,8 @@ paths:
             format: uuid
             type: string
       responses:
-        "202":
-          description: Accepted.
+        "204":
+          description: No Content.
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:
@@ -208867,7 +208867,7 @@ paths:
         Escalates an On-Call Page.
       operationId: EscalateOnCallPage
       parameters:
-        - description: The page ID.
+        - description: The Page ID.
           in: path
           name: page_id
           required: true
@@ -208876,8 +208876,8 @@ paths:
             format: uuid
             type: string
       responses:
-        "202":
-          description: Accepted.
+        "204":
+          description: No Content.
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:
@@ -208969,7 +208969,7 @@ paths:
         Reroutes an On-Call Page.
       operationId: RerouteOnCallPage
       parameters:
-        - description: The page ID.
+        - description: The Page ID.
           in: path
           name: page_id
           required: true
@@ -209105,7 +209105,7 @@ paths:
         Resolves an On-Call Page.
       operationId: ResolveOnCallPage
       parameters:
-        - description: The page ID.
+        - description: The Page ID.
           in: path
           name: page_id
           required: true
@@ -209114,8 +209114,8 @@ paths:
             format: uuid
             type: string
       responses:
-        "202":
-          description: Accepted.
+        "204":
+          description: No Content.
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:

examples/v2/on-call-paging/AcknowledgeOnCallPage.py

@@ -1,5 +1,5 @@
 """
-Acknowledge On-Call Page returns "Accepted." response
+Acknowledge On-Call Page returns "No Content." response
 """
 
 from os import environ

examples/v2/on-call-paging/CreateOnCallPage.py

@@ -1,5 +1,5 @@
 """
-Create On-Call Page returns "OK." response
+Create On-Call Page returns "Created." response
 """
 
 from os import environ

examples/v2/on-call-paging/EscalateOnCallPage.py

@@ -1,5 +1,5 @@
 """
-Escalate On-Call Page returns "Accepted." response
+Escalate On-Call Page returns "No Content." response
 """
 
 from os import environ

examples/v2/on-call-paging/ResolveOnCallPage.py

@@ -1,5 +1,5 @@
 """
-Resolve On-Call Page returns "Accepted." response
+Resolve On-Call Page returns "No Content." response
 """
 
 from os import environ

src/datadog_api_client/v2/api/on_call_paging_api.py

@@ -489,7 +489,7 @@ def acknowledge_on_call_page(
 
         Acknowledges an On-Call Page.
 
-        :param page_id: The page ID.
+        :param page_id: The Page ID.
         :type page_id: UUID
         :rtype: None
         """
@@ -522,7 +522,7 @@ def escalate_on_call_page(
 
         Escalates an On-Call Page.
 
-        :param page_id: The page ID.
+        :param page_id: The Page ID.
         :type page_id: UUID
         :rtype: None
         """
@@ -540,7 +540,7 @@ def reroute_on_call_page(
 
         Reroutes an On-Call Page.
 
-        :param page_id: The page ID.
+        :param page_id: The Page ID.
         :type page_id: UUID
         :type body: RerouteOnCallPageRequest
         :rtype: None
@@ -560,7 +560,7 @@ def resolve_on_call_page(
 
         Resolves an On-Call Page.
 
-        :param page_id: The page ID.
+        :param page_id: The Page ID.
         :type page_id: UUID
         :rtype: None
         """

src/datadog_api_client/v2/model/create_page_request_data_attributes.py

@@ -59,13 +59,13 @@ def __init__(
         :param description: A short summary of the issue or context.
         :type description: str, optional
 
-        :param tags: Tags to help categorize or filter the page.
+        :param tags: Tags to help categorize or filter the Page.
         :type tags: [str], optional
 
         :param target: Information about the target to notify (such as a team or user).
         :type target: CreatePageRequestDataAttributesTarget
 
-        :param title: The title of the page.
+        :param title: The title of the Page.
         :type title: str
 
         :param urgency: On-Call Page urgency level.

src/datadog_api_client/v2/model/create_page_response.py

@@ -34,7 +34,7 @@ def __init__(self_, data: Union[CreatePageResponseData, UnsetType] = unset, **kw
         """
         The full response object after creating a new On-Call Page.
 
-        :param data: The information returned after successfully creating a page.
+        :param data: The information returned after successfully creating a Page.
         :type data: CreatePageResponseData, optional
         """
         if data is not unset:

src/datadog_api_client/v2/model/create_page_response_data.py

@@ -34,9 +34,9 @@ def openapi_types(_):
 
     def __init__(self_, type: CreatePageResponseDataType, id: Union[str, UnsetType] = unset, **kwargs):
         """
-        The information returned after successfully creating a page.
+        The information returned after successfully creating a Page.
 
-        :param id: The unique ID of the created page.
+        :param id: The unique ID of the created Page.
         :type id: str, optional
 
         :param type: The type of resource used when creating an On-Call Page.

src/datadog_api_client/v2/model/reroute_on_call_page_request_data_attributes.py

@@ -42,7 +42,7 @@ def __init__(
         """
         Details about where to reroute the On-Call Page.
 
-        :param comment: An optional comment explaining why the page is being rerouted.
+        :param comment: An optional comment explaining why the Page is being rerouted.
         :type comment: str, optional
 
         :param target: Information about the target to notify (such as a team or user).

tests/v2/features/on-call_paging.feature

@@ -10,25 +10,25 @@ Feature: On-Call Paging
     And an instance of "On-CallPaging" API
 
   @generated @skip @team:ddoghq/on-call
-  Scenario: Acknowledge On-Call Page returns "Accepted." response
+  Scenario: Acknowledge On-Call Page returns "No Content." response
     Given new "AcknowledgeOnCallPage" request
     And request contains "page_id" parameter from "REPLACE.ME"
     When the request is sent
-    Then the response status is 202 Accepted.
+    Then the response status is 204 No Content.
 
   @generated @skip @team:ddoghq/on-call
-  Scenario: Create On-Call Page returns "OK." response
+  Scenario: Create On-Call Page returns "Created." response
     Given new "CreateOnCallPage" request
     And body with value {"data": {"attributes": {"description": "Page details.", "tags": ["service:test"], "target": {"identifier": "my-team", "type": "team_handle"}, "title": "Page title", "urgency": "low"}, "type": "pages"}}
     When the request is sent
-    Then the response status is 200 OK.
+    Then the response status is 201 Created.
 
   @generated @skip @team:ddoghq/on-call
-  Scenario: Escalate On-Call Page returns "Accepted." response
+  Scenario: Escalate On-Call Page returns "No Content." response
     Given new "EscalateOnCallPage" request
     And request contains "page_id" parameter from "REPLACE.ME"
     When the request is sent
-    Then the response status is 202 Accepted.
+    Then the response status is 204 No Content.
 
   @generated @skip @team:ddoghq/on-call
   Scenario: Reroute On-Call Page returns "Bad Request" response
@@ -47,8 +47,8 @@ Feature: On-Call Paging
     Then the response status is 204 No Content.
 
   @generated @skip @team:ddoghq/on-call
-  Scenario: Resolve On-Call Page returns "Accepted." response
+  Scenario: Resolve On-Call Page returns "No Content." response
     Given new "ResolveOnCallPage" request
     And request contains "page_id" parameter from "REPLACE.ME"
     When the request is sent
-    Then the response status is 202 Accepted.
+    Then the response status is 204 No Content.