From 38bc6e575adc2f1bd50e7ac3dbf05b232df2715a Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Sun, 9 Nov 2025 19:21:03 +0000 Subject: [PATCH] Regenerate client from commit 901655b of spec repo --- .../resources/com/datadog/api/client/v2/api/monitors.feature | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/test/resources/com/datadog/api/client/v2/api/monitors.feature b/src/test/resources/com/datadog/api/client/v2/api/monitors.feature index 346a646f83b..a8267c72b90 100644 --- a/src/test/resources/com/datadog/api/client/v2/api/monitors.feature +++ b/src/test/resources/com/datadog/api/client/v2/api/monitors.feature @@ -233,7 +233,10 @@ Feature: Monitors And operation "ListMonitorUserTemplates" enabled When the request is sent Then the response status is 200 OK - And the response "data" has length 1 + And the response "data" has item with field "type" with value "monitor-user-template" + And the response "data" has item with field "id" with value "{{ monitor_user_template.data.id }}" + And the response "data" has item with field "attributes.description" with value "It's a threshold" + And the response "data" has item with field "attributes.monitor_definition.message" with value "cats" @skip-validation @team:DataDog/monitor-app Scenario: Update a monitor notification rule returns "Bad Request" response