Document missing limitations and 409 response for org disable endpoint

.generator/schemas/v2/openapi.yaml

@@ -31063,9 +31063,17 @@ components:
           type: string
         values:
           description: |-
-            Column values in row order. The element type matches the column's `type`;
-            for example a `VARCHAR` column carries strings, a `TIMESTAMP` column carries
-            Unix-millisecond integers. `null` is allowed for missing values.
+            Column values in row order, one entry per result row. The element type
+            follows the column's `type`. The following serialization rules should be
+            taken into account:
+
+            - `BIGINT` values are encoded as JSON numbers in the signed 64-bit integer range.
+            - `DECIMAL` values are encoded as JSON numbers with 64-bit double precision.
+            - `TIMESTAMP` and `DATE` values are encoded as Unix-millisecond integers; a
+              `DATE` resolves to midnight UTC.
+            - `JSON` values are returned as a JSON-encoded string.
+
+            `null` is allowed for any column type where a value is missing.
           example:
             - web-store
             - checkout
@@ -135602,9 +135610,6 @@ paths:
       summary: Execute a tabular DDSQL query
       tags:
         - DDSQL
-      x-unstable: |-
-        **Note**: This endpoint is in preview and is subject to change.
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/ddsql/query/tabular/fetch:
     post:
       description: |-
@@ -135713,9 +135718,6 @@ paths:
       summary: Fetch the result of a DDSQL query
       tags:
         - DDSQL
-      x-unstable: |-
-        **Note**: This endpoint is in preview and is subject to change.
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/deletion/data/{product}:
     post:
       description: Creates a data deletion request by providing a query and a timeframe targeting the proper data.
@@ -166072,6 +166074,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:
@@ -166120,6 +166134,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

lib/datadog_api_client/configuration.rb

@@ -432,8 +432,6 @@ def initialize
             "v2.get_all_datasets": false,
             "v2.get_dataset": false,
             "v2.update_dataset": false,
-            "v2.execute_ddsql_tabular_query": false,
-            "v2.fetch_ddsql_tabular_query": false,
             "v2.cancel_data_deletion_request": false,
             "v2.create_data_deletion_request": false,
             "v2.get_data_deletion_requests": false,

lib/datadog_api_client/v2/api/customer_org_api.rb

@@ -39,6 +39,18 @@ def disable_customer_org(body, opts = {})
     # 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 body [CustomerOrgDisableRequest] 
     # @param opts [Hash] the optional parameters
     # @return [Array<(CustomerOrgDisableResponse, Integer, Hash)>] CustomerOrgDisableResponse data, response status code and response headers

lib/datadog_api_client/v2/api/ddsql_api.rb

@@ -41,12 +41,6 @@ def execute_ddsql_tabular_query(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(DdsqlTabularQueryResponse, Integer, Hash)>] DdsqlTabularQueryResponse data, response status code and response headers
     def execute_ddsql_tabular_query_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.execute_ddsql_tabular_query".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.execute_ddsql_tabular_query")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.execute_ddsql_tabular_query"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: DDSQLAPI.execute_ddsql_tabular_query ...'
@@ -117,12 +111,6 @@ def fetch_ddsql_tabular_query(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(DdsqlTabularQueryResponse, Integer, Hash)>] DdsqlTabularQueryResponse data, response status code and response headers
     def fetch_ddsql_tabular_query_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.fetch_ddsql_tabular_query".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.fetch_ddsql_tabular_query")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.fetch_ddsql_tabular_query"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: DDSQLAPI.fetch_ddsql_tabular_query ...'

lib/datadog_api_client/v2/models/ddsql_tabular_query_column.rb

@@ -31,9 +31,17 @@ class DdsqlTabularQueryColumn
     # for the full, up-to-date list.
     attr_reader :type
 
-    # Column values in row order. The element type matches the column's `type`;
-    # for example a `VARCHAR` column carries strings, a `TIMESTAMP` column carries
-    # Unix-millisecond integers. `null` is allowed for missing values.
+    # Column values in row order, one entry per result row. The element type
+    # follows the column's `type`. The following serialization rules should be
+    # taken into account:
+    #
+    # - `BIGINT` values are encoded as JSON numbers in the signed 64-bit integer range.
+    # - `DECIMAL` values are encoded as JSON numbers with 64-bit double precision.
+    # - `TIMESTAMP` and `DATE` values are encoded as Unix-millisecond integers; a
+    #   `DATE` resolves to midnight UTC.
+    # - `JSON` values are returned as a JSON-encoded string.
+    #
+    # `null` is allowed for any column type where a value is missing.
     attr_reader :values
 
     attr_accessor :additional_properties