glesys_dnsdomain_record loses track of TTL if field is unset
Closed this issue · 2 comments
tazjin commented
If a glesys_dnsdomain_record
is configured with a TTL, and the explicit TTL setting is later removed (e.g. in order to revert to the default value) the provider loses track of this and does not attempt to reconcile the TTL.
This can cause problems if somebody assumes that the setting has been reverted back to the 3600 second default.
norrland commented
Do you have any example of this?
As the TTL field is optional, removing this from the terraform configuration will not instruct the provider to set a default TTL.
Doing a terraform refresh && terraform show
would still show the current TTL value for a record.
norrland commented
Please reopen if still relevant.