The provided terraform configuration is for only one alert type, but the same issue happens with any other alert type I tested:
End-to-End (Server)
End-to-End (Agent)
Voice
HTTP Server
Page Load
DNS Trace
DNS Server
BGP
I can provide examples for all the above if needed.
Steps to reproduce the bug
Run terraform apply
Check the Alert Rule in the UI to confirm it is associated with a Test.
Modify the thousandeyes_alert_rule. For example, change the rounds_violating_required value from 3 to 4.
Apply the change: terraform apply
Check the Alert Rule in the UI to confirm it is NOT associated with any Test.
A workaround to get the associations back is to replace the Terraform resource. Running the command below will re-associate the provided alert rule with the test:
What versions are you using?
What did you expect to happen?
When a change is made to a
thousandeyes_alert_rule
resource associated with one or more tests, the association is expected to remain the same.What actually happened?
When a change is made to a
thousandeyes_alert_rule
resource, all tests are disassociated from that alert rule.Terraform code to reproduce the bug
Any additional comments or code?
The provided terraform configuration is for only one alert type, but the same issue happens with any other alert type I tested:
I can provide examples for all the above if needed.
Steps to reproduce the bug
terraform apply
thousandeyes_alert_rule
. For example, change therounds_violating_required
value from3
to4
.terraform apply
A workaround to get the associations back is to replace the Terraform resource. Running the command below will re-associate the provided alert rule with the test:
Sample captures: