BetterStackHQ/terraform-provider-better-uptime

Impossible to disable domain_expiration check after being set

Closed this issue · 3 comments

I wish to disable the domain expiration check for various monitors we have configured. Unfortunately, it appears to not be possible to disable this check via Terraform once it has been set.

I receive the Domain expiration is invalid. Valid values are: [nil, 1, 2, 3, 7, 14, 30, 60] error no matter what I do.

  • Omitting the property results in the error.
  • Changing the value to the string "nil" results in the error.
  • Changing the value to the number 0 results in the error.

It appears the only way to disable the check, is to manually edit the entries in the UI and then remove the line from the TF file.

Hi there Justin,

It's Filip from Better Stack's team here jumping in.

Thanks a lot for your message and our sincere apologies for the inconvenience.

We've had a look into this and this seems to be caused by a discrepancy between Terraform and what we expect. We'll look into fixing this and will keep you updated on any progress. Thanks a lot for bringing this up, Justin! 🙌

In the meantime, if you'd like to update more monitors at once, feel free to shoot us a message at "hello@betterstack.com" and we'd be happy to bulk update the monitors for you, so you could then just remove the line from the TF file. :)

Happy to assist further with that or if anything else comes up.

Thanks a lot!

Kind regards,
Filip

Hello,

William from Better Stack here. I apologise once again for the troubles.

After checking the issue it seems that it is now possible to both create resources with domain_expiration = null and modify domain_expiration of existing resources to null. That said, I noticed a warning message regarding null values and legacy Terraform SDK.
image

Following my previous message, it looks like the issue has been resolved.