You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading from 0.28.0 to 0.29.0, terraform wants to force replace the container and iso images I've created earlier to add the timeout_upload value. As a consequence, the already created containers also had to be re-created.
To Reproduce
Steps to reproduce the behavior:
Using provider with version 0.28.0, create a proxmox_virtual_environment_file with type vztmpl or iso
Describe the bug
After upgrading from 0.28.0 to 0.29.0, terraform wants to force replace the container and iso images I've created earlier to add the
timeout_upload
value. As a consequence, the already created containers also had to be re-created.To Reproduce
Steps to reproduce the behavior:
proxmox_virtual_environment_file
with typevztmpl
oriso
Example resource:
Expected behavior
The upload timeout should not require force-replacement.
Workaround
After upgrading to 0.29.0, set the
timeout_upload = 0
for all existing images.Screenshots
After upgrading to 0.29 (or any newer) without workaround, a fragment from
terraform plan
In addition, all dependant containers have to be replaced.
Additional context
Add any other context about the problem here.
TF_LOG=DEBUG terraform apply
): not additional info thereThe text was updated successfully, but these errors were encountered: