Pierre Lafievre

Just to be sure I get this sentence part: ```This should therefore only impact resources that don't or can't update all their fields in Get``` I may be confused due...

I may want to give it a try using https://github.com/openai/openai-go if I have some success with my other PRs

Running `TF_LOG=TRACE TF_LOG_PATH=terraform.log terraform apply` you'll have some more logs, it may help. There's a chance to see this message in logs: "[INFO] ignore disk without image_id and type" Digging...

The current provider behavior when updating the `ip4` attribute is to detach then reattach the address range. There's an update_ar XML-RPC method and the provider use it but it doesn't...

Similar to older work (not merged): issue: https://github.com/OpenNebula/terraform-provider-opennebula/issues/318 PR: https://github.com/OpenNebula/terraform-provider-opennebula/pull/323

It's a documentation error, `template` was already removed a long time ago: https://github.com/OpenNebula/terraform-provider-opennebula/pull/170/files#diff-9f084ea0f99816f2b1d2804d73954a89b60f71f29105da84ea55251df14e0237L35 It was removed via PR #170: i.e. when I refactored template resources to share a lot of...

Thanks for reporting this, we'll schedule this in a release and I'll take a look as soon as possible

Sorry for the late reply, it seems it was a small error in the code, feel free to test the fix in the PR I just created

It seems `cpumodel` sections of the virtual machine resource is missing in the documentation, we need at least a PR to update the documentation. See an usage example here: https://github.com/OpenNebula/terraform-provider-opennebula/blob/master/opennebula/resource_opennebula_virtual_machine_test.go#L605...

I suppose that we should introduce a new datasource `opennebula_virtual_machines` to be consistent with the `openenbula_templates` datasource introduced by #322 [See doc](https://registry.terraform.io/providers/OpenNebula/opennebula/latest/docs/data-sources/templates)