From 422dc1bf171f2010081e5dedbb26313bcb684c22 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Tue, 28 Jul 2026 18:08:37 +0000 Subject: [PATCH] Regenerate client from commit ad5a583 of spec repo --- .generator/schemas/v2/openapi.yaml | 20 +++++++++------- features/v2/org_connections.feature | 6 ++--- features/v2/synthetics_setup.json | 24 +++++++++++++++++++ .../configuration.ts | 2 -- .../datadog-api-client-v2/apis/DDSQLApi.ts | 14 ----------- .../models/DdsqlTabularQueryColumn.ts | 14 ++++++++--- 6 files changed, 49 insertions(+), 31 deletions(-) create mode 100644 features/v2/synthetics_setup.json diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index acd63e70a663..0f274c232a0d 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.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. diff --git a/features/v2/org_connections.feature b/features/v2/org_connections.feature index f829284f442f..1320c514074b 100644 --- a/features/v2/org_connections.feature +++ b/features/v2/org_connections.feature @@ -32,7 +32,7 @@ Feature: Org Connections When the request is sent Then the response status is 404 Not Found - @team:DataDog/access-enforcement + @synthetics-setup(org_connections_cleanup) @team:DataDog/access-enforcement Scenario: Create Org Connection returns "OK" response Given new "CreateOrgConnections" request And body with value {"data": {"type": "org_connection", "relationships": {"sink_org": {"data": {"type": "orgs", "id": "83999dcd-7f97-11f0-8de1-1ecf66f1aa85"}}}, "attributes": {"connection_types": ["logs"]}}} @@ -53,7 +53,7 @@ Feature: Org Connections When the request is sent Then the response status is 404 Not Found - @team:DataDog/access-enforcement + @synthetics-setup(org_connections_cleanup) @team:DataDog/access-enforcement Scenario: Delete Org Connection returns "OK" response Given there is a valid "org_connection" in the system And new "DeleteOrgConnections" request @@ -85,7 +85,7 @@ Feature: Org Connections When the request is sent Then the response status is 404 Not Found - @team:DataDog/access-enforcement + @synthetics-setup(org_connections_cleanup) @team:DataDog/access-enforcement Scenario: Update Org Connection returns "OK" response Given there is a valid "org_connection" in the system And new "UpdateOrgConnections" request diff --git a/features/v2/synthetics_setup.json b/features/v2/synthetics_setup.json new file mode 100644 index 000000000000..d3bd8bb89fe7 --- /dev/null +++ b/features/v2/synthetics_setup.json @@ -0,0 +1,24 @@ +{ + "org_connections_cleanup": [ + { + "name": "remove an existing org connection for the test sink org", + "method": "GET", + "url": "https://api.{{ DD_TEST_SITE_2 }}/api/v2/org_connections", + "no_saving_response_body": false, + "headers": { + "Accept": "application/json" + }, + "extracted_values": [ + { + "name": "EXISTING_ORG_CONNECTION_DATA_ID", + "value": "$.data[?(@.relationships.source_org.data.id == '4dee724d-00cc-11ea-a77b-570c9d03c6c5' && @.relationships.sink_org.data.id == '83999dcd-7f97-11f0-8de1-1ecf66f1aa85')].id" + } + ] + }, + { + "name": "delete an existing org connection for the test sink org", + "method": "DELETE", + "url": "https://api.{{ DD_TEST_SITE_2 }}/api/v2/org_connections/{{ EXISTING_ORG_CONNECTION_DATA_ID }}" + } + ] +} diff --git a/packages/datadog-api-client-common/configuration.ts b/packages/datadog-api-client-common/configuration.ts index 19dfbf786199..f4f4ee937ed8 100644 --- a/packages/datadog-api-client-common/configuration.ts +++ b/packages/datadog-api-client-common/configuration.ts @@ -465,8 +465,6 @@ export function createConfiguration( "v2.getAllDatasets": false, "v2.getDataset": false, "v2.updateDataset": false, - "v2.executeDdsqlTabularQuery": false, - "v2.fetchDdsqlTabularQuery": false, "v2.cancelDataDeletionRequest": false, "v2.createDataDeletionRequest": false, "v2.getDataDeletionRequests": false, diff --git a/packages/datadog-api-client-v2/apis/DDSQLApi.ts b/packages/datadog-api-client-v2/apis/DDSQLApi.ts index 4b771bb87cb7..07ec8e65af52 100644 --- a/packages/datadog-api-client-v2/apis/DDSQLApi.ts +++ b/packages/datadog-api-client-v2/apis/DDSQLApi.ts @@ -29,13 +29,6 @@ export class DDSQLApiRequestFactory extends BaseAPIRequestFactory { ): Promise { const _config = _options || this.configuration; - logger.warn("Using unstable operation 'executeDdsqlTabularQuery'"); - if (!_config.unstableOperations["v2.executeDdsqlTabularQuery"]) { - throw new Error( - "Unstable operation 'executeDdsqlTabularQuery' is disabled" - ); - } - // verify required parameter 'body' is not null or undefined if (body === null || body === undefined) { throw new RequiredError("body", "executeDdsqlTabularQuery"); @@ -77,13 +70,6 @@ export class DDSQLApiRequestFactory extends BaseAPIRequestFactory { ): Promise { const _config = _options || this.configuration; - logger.warn("Using unstable operation 'fetchDdsqlTabularQuery'"); - if (!_config.unstableOperations["v2.fetchDdsqlTabularQuery"]) { - throw new Error( - "Unstable operation 'fetchDdsqlTabularQuery' is disabled" - ); - } - // verify required parameter 'body' is not null or undefined if (body === null || body === undefined) { throw new RequiredError("body", "fetchDdsqlTabularQuery"); diff --git a/packages/datadog-api-client-v2/models/DdsqlTabularQueryColumn.ts b/packages/datadog-api-client-v2/models/DdsqlTabularQueryColumn.ts index 4b1c1395944a..e16fb0f2402d 100644 --- a/packages/datadog-api-client-v2/models/DdsqlTabularQueryColumn.ts +++ b/packages/datadog-api-client-v2/models/DdsqlTabularQueryColumn.ts @@ -23,9 +23,17 @@ export class DdsqlTabularQueryColumn { */ "type": string; /** - * 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. */ "values": Array;