Pavel Boldyrev

There is a [logic](https://github.com/bpg/terraform-provider-proxmox/blob/2a56c23f52abda293f328196a0d80b9becd749a7/proxmoxtf/resource/file.go#L767-L769) in the file resource to detect _local file_ changes (i.e. for `source_file` pointing to file in a file system, not URL). Though it may not work...

Thanks! I remember this feature worked for me, a caused unexpected recreation of a working VM because the source disk image has changed 🤦🏼‍♂️ I'll try adding some [acceptance tests](https://github.com/bpg/terraform-provider-proxmox/blob/2a56c23f52abda293f328196a0d80b9becd749a7/fwprovider/tests/resource_file_test.go)...

Also related: - https://github.com/bpg/terraform-provider-proxmox/issues/360

If one needs to protect sensitive values in the state, OpenTofu's [State Encryption](https://opentofu.org/docs/language/state/encryption/) feature is a good option.

At this stage I don't think separating Proxmox API client from the provider will be beneficial. We keep changing the API layer, and separation only adds to the maintenance headache.

See also #1231

This seems to be related to handling of empty blocks. This particular error is related to an empty `initialization.dns` in the plan. Related: - https://github.com/bpg/terraform-provider-proxmox/pull/1043 - https://github.com/bpg/terraform-provider-proxmox/pull/977 Also in VM:...

leave it :)

> Btw. the provider does not seem to connect to the API during plan stage. It does call read, but only if there is a local state to compare with....

Hi @Tash1nka! >1. Being able to connect throught an SSH bastion host Will be addressed in #852 >2. Being able to resolve hostnames for the nodes addresses Added in #848...