We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
contentRegex
username
password
customHeaders
alertRules
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The ThousandEyes API misses updating back to empty fields. For example:
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.
The text was updated successfully, but these errors were encountered: