Open gbloquel opened 3 days ago
I have found an explanation.
My resource freebox_virtual_machine
has been imported in version 1.1.1
Below the state of timeouts
$ terraform state show freebox_virtual_machine.homeassistant # freebox_virtual_machine.homeassistant: resource "freebox_virtual_machine" "homeassistant" { ... timeouts = { create = "5m" delete = "5m" kill = "30s" read = "5m" update = "5m" } }
In the version 1.2.0 you added the networking
field in the timeouts
the networking was not available and after I switch into 1.2.0 the terraform plan
produces Duration string value is null
for the field networking
.
Workaround:
terraform state rm freebox_virtual_machine.homeassistant
terraform plan
works and in the terraform state the networking field will be available.terraform state show freebox_virtual_machine.homeassistant # freebox_virtual_machine.homeassistant: resource "freebox_virtual_machine" "homeassistant" { ... timeouts = { create = "5m" delete = "5m" kill = "30s" networking = "1m" read = "5m" update = "5m" } ... }
Hi @gbloquel
Indeed the new version has a new timeout field which I did not bother to properly write the upgrade code for ; my apologies for that.
I'll make a fix for any other user that might be impacted.
Thanks for the feedback and happy to see that someone else than me is finding some usefulness in this niche provider.
Cheers
Hi @NikolaLohinski,
I have upgraded your provider from (1.1.1) to your latest version (1.2.0).
After the upgrade no way to
terraform plan
. I have the following messageAs the error indicates a problem with the duration I tried to override the embedded properties of timeouts but the problem seems to be elsewhere.
I have also activated the terraform logs in trace mode. but nothing interesting I think