❯ terraform version
Terraform v1.6.6
on darwin_amd64
+ provider registry.terraform.io/thousandeyes/thousandeyes v2.0.6
What did you expect to happen?
When creating new ThousandEyes tests, if the mtu_measurements parameter value is set to false, the test resources must be created with mtu_measurements=false.
What actually happened?
When creating new tests with any of the resources listed below, if the mtu_measurements parameter value is set to false, its value is ignored, and the tests are created with mtu_measurements = true.
After the test resources are created, if you run terraform apply for a 2nd time, the mtu_measurements value changes from true to false as they should be according to the Terraform configuration.
What versions are you using?
What did you expect to happen?
When creating new ThousandEyes tests, if the
mtu_measurements
parameter value is set tofalse
, the test resources must be created withmtu_measurements=false
.What actually happened?
When creating new tests with any of the resources listed below, if the
mtu_measurements
parameter value is set tofalse
, its value is ignored, and the tests are created withmtu_measurements = true
.After the test resources are created, if you run
terraform apply
for a 2nd time, themtu_measurements
value changes fromtrue
tofalse
as they should be according to the Terraform configuration.This issue happens for the following resources:
Terraform code to reproduce the bug
Any additional comments or code?
No response
Steps to reproduce the bug
terraform apply -auto-approve
Workaround If you want the
mtu_measurements
false value to be considered, runterraform apply
again.Example: The following example uses the terraform configuration provided to reproduce the issue.
Workaround
As seen above, the value will change for all tests:
~ mtu_measurements = true -> false
.