Regenerate client from commit d998cc7 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -165921,6 +165921,18 @@ paths:
         the authenticated org or the request is rejected. Successful calls disable the org
         and return the resulting state from the downstream service. Requires the
         `org_management` permission.
+
+        **Limitations**:
+
+        - **Organization age**: Only organizations created within the last 10 days can be disabled
+          through this endpoint. This restriction is a safeguard against accidentally disabling
+          long-running organizations. Attempting to disable an older organization returns a `403 Forbidden`.
+        - **Feature flag**: The feature flag `org_disable_self_service_enabled` must be enabled for the
+          target organization or one of its ancestor organizations. Contact
+          [Datadog support](https://docs.datadoghq.com/help/) to enable this for your organization.
+          Requests for organizations without this flag return a `403 Forbidden`.
+        - **Already-disabled organizations**: If the target organization is already disabled, the request
+          returns a `409 Conflict`.
       operationId: DisableCustomerOrg
       requestBody:
         content:
@@ -165969,6 +165981,12 @@ paths:
               schema:
                 $ref: "#/components/schemas/JSONAPIErrorResponse"
           description: Forbidden
+        "409":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Conflict
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
         "500":

features/v2/customer_org.feature

@@ -17,6 +17,11 @@ Feature: Customer Org
     When the request is sent
     Then the response status is 400 Bad Request
 
+  @generated @skip @team:DataDog/org-management
+  Scenario: Disable the authenticated customer organization returns "Conflict" response
+    When the request is sent
+    Then the response status is 409 Conflict
+
   @generated @skip @team:DataDog/org-management
   Scenario: Disable the authenticated customer organization returns "OK" response
     When the request is sent

packages/datadog-api-client-v2/apis/CustomerOrgApi.ts

@@ -95,6 +95,7 @@ export class CustomerOrgApiResponseProcessor {
       response.httpStatusCode === 400 ||
       response.httpStatusCode === 401 ||
       response.httpStatusCode === 403 ||
+      response.httpStatusCode === 409 ||
       response.httpStatusCode === 500
     ) {
       const bodyText = ObjectSerializer.parse(
@@ -188,6 +189,18 @@ export class CustomerOrgApi {
    * the authenticated org or the request is rejected. Successful calls disable the org
    * and return the resulting state from the downstream service. Requires the
    * `org_management` permission.
+   *
+   * **Limitations**:
+   *
+   * - **Organization age**: Only organizations created within the last 10 days can be disabled
+   *   through this endpoint. This restriction is a safeguard against accidentally disabling
+   *   long-running organizations. Attempting to disable an older organization returns a `403 Forbidden`.
+   * - **Feature flag**: The feature flag `org_disable_self_service_enabled` must be enabled for the
+   *   target organization or one of its ancestor organizations. Contact
+   *   [Datadog support](https://docs.datadoghq.com/help/) to enable this for your organization.
+   *   Requests for organizations without this flag return a `403 Forbidden`.
+   * - **Already-disabled organizations**: If the target organization is already disabled, the request
+   *   returns a `409 Conflict`.
    * @param param The request object
    */
   public disableCustomerOrg(