But always hardcoding the default value has a side effect: the UI says that 1 option is configured, which isn't exactly right when users do not have a request_definition.timeout set in TF.
Our backend now ignores 0 for a timeout, so we can remove the default value from TF and ensure the change is backwards compatible (i.e. doesn't generate diffs when planning/applying)
This is a PR stack, here is how it's organized:
In https://github.com/DataDog/terraform-provider-datadog/pull/1497, we added the same value in TF as in the UI to fix a bug where the timeout was set to
0.But always hardcoding the default value has a side effect: the UI says that 1 option is configured, which isn't exactly right when users do not have a
request_definition.timeoutset in TF.Our backend now ignores
0for a timeout, so we can remove the default value from TF and ensure the change is backwards compatible (i.e. doesn't generate diffs when planning/applying)