Terraform doesn't regenerate cloud-init image on changes
Closed this issue · 3 comments
It looks like the terraform provide doesn't "regenerate" the cloud init image when changes are performed. As an example, if I assign the IP 192.168.4.100 to a VM, run terraform apply, change the IP to 192.168.4.101, run terraform apply again, here is what happens the modification is correctly performed by Terraform:
... but proxmox shows that the cloud init image needs to be regenerated:
More precisely, I need to manually click the "Regenerate image" button in order for changes to take effect.
Any chance to have this capability integrated in the provider? FYI, here's the API request made when the button is pressed:
PUT /api2/extjs/nodes/proxmox/qemu/102/config HTTP/1.1
Host: proxmox.home:8006
ide0=nas-nfs-main%3Acloudinit
(nas-nfs-main is the name of my storage pool)
This would require work in the Proxmox API Go repository. Specifically, I guess it requires a method to be added in the client.
Alright, maybe out of scope for this repository then? Still, seems like an important feature to have because it essentially breaks automation if you want to use cloud init
Well, it doesn't break it. You cannot play tennis with IP addresses; that is another story. The API go repo is maintained by the same person as this repo. If you are capable, maybe you can create a PR at that repo? Then I can help getting the feature in here.