Skip to content

[monitors] Avoid inconsistent result in production for user templates #3241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −1
Open

[monitors] Avoid inconsistent result in production for user templates #3241

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/test/resources/com/datadog/api/client/v2/api/monitors.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading