From 6dfe5faa0d135e27f8fec4cc01bdc9f425ef01d4 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Tue, 24 Feb 2026 14:43:08 +0000 Subject: [PATCH] Regenerate client from commit 1ceefea of spec repo --- features/v2/monitors.feature | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/features/v2/monitors.feature b/features/v2/monitors.feature index e84062637c1a..b1bb50a8dbf3 100644 --- a/features/v2/monitors.feature +++ b/features/v2/monitors.feature @@ -241,7 +241,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