Skip to content
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.

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

Support updating back to empty fields #105

Open
raul-te opened this issue Jul 11, 2022 · 0 comments
Open

Support updating back to empty fields #105

raul-te opened this issue Jul 11, 2022 · 0 comments

Comments

@raul-te
Copy link
Collaborator

raul-te commented Jul 11, 2022

The ThousandEyes API misses updating back to empty fields. For example:

$ curl -d '{"contentRegex":"Needle"}' -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer redacted" https://api.thousandeyes.com/v6/tests/http-server/<test_number>/update

$ curl -sd '{"contentRegex":""}' -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Bearer redacted" https://api.thousandeyes.com/v6/tests/http-server/<test_number>/update | jq | grep Needle
      "contentRegex": "Needle",

It happens in many fields, such as contentRegex, username, password, customHeaders, alertRules, etc.

This is a limitation. For example, it's not possible to disable alert rules entirely if an alert rule was already defined.

This issue has been reported internally and a fix is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant