From bec09cf36d3cc2e2fcf84eece0744d163de7ec96 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Wed, 21 Oct 2026 13:54:12 +0000 Subject: [PATCH] Regenerate client from commit e78ef8d of spec repo --- .generator/schemas/v2/openapi.yaml | 30 ++++++++++++++----- .../v2/api/network_device_monitoring_api.py | 4 +-- .../network_device_monitoring.feature | 16 ++++++++++ 3 files changed, 41 insertions(+), 9 deletions(-) diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index 29872b8b53..dd0d53a8e4 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.generator/schemas/v2/openapi.yaml @@ -2381,6 +2381,18 @@ components: schema: $ref: "#/components/schemas/HTTPCDRulesNotFoundResponse" description: Deployment rule not found. + NDMBadRequestResponse: + content: + application/json: + schema: + $ref: "#/components/schemas/JSONAPIErrorResponse" + description: Bad Request + NDMNotFoundResponse: + content: + application/json: + schema: + $ref: "#/components/schemas/JSONAPIErrorResponse" + description: Not Found NotAuthorizedResponse: content: "application/json": @@ -203394,7 +203406,7 @@ paths: parameters: - $ref: "#/components/parameters/NDMPageSize" - $ref: "#/components/parameters/NDMPageNumber" - - description: The field to sort the devices by. Defaults to `name`. + - description: The field to sort devices by. Defaults to `name`. Prefix the field with `-` to sort in descending order, for example, `-name`. example: status in: query name: sort @@ -203432,7 +203444,7 @@ paths: $ref: "#/components/schemas/ListDevicesResponse" description: OK "400": - $ref: "#/components/responses/BadRequestResponse" + $ref: "#/components/responses/NDMBadRequestResponse" "403": $ref: "#/components/responses/ForbiddenResponse" "429": @@ -203480,7 +203492,7 @@ paths: "403": $ref: "#/components/responses/ForbiddenResponse" "404": - $ref: "#/components/responses/NotFoundResponse" + $ref: "#/components/responses/NDMNotFoundResponse" "429": $ref: "#/components/responses/TooManyRequestsResponse" summary: Get the device details @@ -203577,7 +203589,7 @@ paths: "403": $ref: "#/components/responses/ForbiddenResponse" "404": - $ref: "#/components/responses/NotFoundResponse" + $ref: "#/components/responses/NDMNotFoundResponse" "429": $ref: "#/components/responses/TooManyRequestsResponse" summary: Get the list of tags for a device @@ -203629,10 +203641,12 @@ paths: schema: $ref: "#/components/schemas/ListTagsResponse" description: OK + "400": + $ref: "#/components/responses/NDMBadRequestResponse" "403": $ref: "#/components/responses/ForbiddenResponse" "404": - $ref: "#/components/responses/NotFoundResponse" + $ref: "#/components/responses/NDMNotFoundResponse" "429": $ref: "#/components/responses/TooManyRequestsResponse" summary: Update the tags for a device @@ -203670,7 +203684,7 @@ paths: "403": $ref: "#/components/responses/ForbiddenResponse" "404": - $ref: "#/components/responses/NotFoundResponse" + $ref: "#/components/responses/NDMNotFoundResponse" "429": $ref: "#/components/responses/TooManyRequestsResponse" summary: List tags for an interface @@ -203720,10 +203734,12 @@ paths: schema: $ref: "#/components/schemas/ListInterfaceTagsResponse" description: OK + "400": + $ref: "#/components/responses/NDMBadRequestResponse" "403": $ref: "#/components/responses/ForbiddenResponse" "404": - $ref: "#/components/responses/NotFoundResponse" + $ref: "#/components/responses/NDMNotFoundResponse" "429": $ref: "#/components/responses/TooManyRequestsResponse" summary: Update the tags for an interface diff --git a/src/datadog_api_client/v2/api/network_device_monitoring_api.py b/src/datadog_api_client/v2/api/network_device_monitoring_api.py index faf83a8138..d9d0efb826 100644 --- a/src/datadog_api_client/v2/api/network_device_monitoring_api.py +++ b/src/datadog_api_client/v2/api/network_device_monitoring_api.py @@ -275,7 +275,7 @@ def list_devices( :type page_size: int, optional :param page_number: Specific page number to return. Defaults to 0. :type page_number: int, optional - :param sort: The field to sort the devices by. Defaults to ``name``. + :param sort: The field to sort devices by. Defaults to ``name``. Prefix the field with ``-`` to sort in descending order, for example, ``-name``. :type sort: str, optional :param filter_tag: Filter devices by tag. :type filter_tag: str, optional @@ -312,7 +312,7 @@ def list_devices_with_pagination( :type page_size: int, optional :param page_number: Specific page number to return. Defaults to 0. :type page_number: int, optional - :param sort: The field to sort the devices by. Defaults to ``name``. + :param sort: The field to sort devices by. Defaults to ``name``. Prefix the field with ``-`` to sort in descending order, for example, ``-name``. :type sort: str, optional :param filter_tag: Filter devices by tag. :type filter_tag: str, optional diff --git a/tests/v2/features/network_device_monitoring.feature b/tests/v2/features/network_device_monitoring.feature index 03c1544583..bcd57861d1 100644 --- a/tests/v2/features/network_device_monitoring.feature +++ b/tests/v2/features/network_device_monitoring.feature @@ -142,6 +142,14 @@ Feature: Network Device Monitoring And the response "data.attributes.tags[0]" is equal to "tag:test" And the response "data.attributes.tags[1]" is equal to "tag:testbis" + @generated @skip @team:ddoghq/network-device-monitoring + Scenario: Update the tags for a device returns "Bad Request" response + Given new "UpdateDeviceUserTags" request + And request contains "device_id" parameter from "REPLACE.ME" + And body with value {"data": {"attributes": {"tags": ["tag:test", "tag:testbis"]}, "id": "example:1.2.3.4"}} + When the request is sent + Then the response status is 400 Bad Request + @replay-only @team:ddoghq/network-device-monitoring Scenario: Update the tags for a device returns "Not Found" response Given new "UpdateDeviceUserTags" request @@ -162,6 +170,14 @@ Feature: Network Device Monitoring And the response "data.attributes.tags[0]" is equal to "tag:test" And the response "data.attributes.tags[1]" is equal to "tag:testbis" + @generated @skip @team:ddoghq/network-device-monitoring + Scenario: Update the tags for an interface returns "Bad Request" response + Given new "UpdateInterfaceUserTags" request + And request contains "interface_id" parameter from "REPLACE.ME" + And body with value {"data": {"attributes": {"tags": ["tag:test", "tag:testbis"]}, "id": "example:1.2.3.4:1"}} + When the request is sent + Then the response status is 400 Bad Request + @replay-only @team:ddoghq/network-device-monitoring Scenario: Update the tags for an interface returns "Not Found" response Given new "UpdateInterfaceUserTags" request