DNS servers block results in unexpected change about terraform-provider-proxmox HOT 4 CLOSED

I can confirm the reported behavior.

To avoid this issue, I added in my code config this lifecycle statement:

lifecycle {
    ignore_changes = [
      initialization
    ]
  }

It seems to be too much (and it is) but, it prevents every unwanted reboots. If I need to change something, I can simply rebuild the instance.

from terraform-provider-proxmox.

Looks like mea culpa in #832

It was an attempt to add servers without breaking change of server but well 😢

Thinking fast, maybe providing both attributes will be temporary fix? Or just downgrade to v0.41.0

resource "proxmox_virtual_environment_vm" "k3s_server_vm" {
  initialization {
    dns {
      server = "10.91.1.1"
      servers = ["10.91.1.1"]
    }
    ...
  }
  ...
}

from terraform-provider-proxmox.

Let me take a look... 👀

from terraform-provider-proxmox.

I had noticed this as well. I was going to look into trying to see if there would be a way to put in some logic to maybe check if servers was being used then to ignore the server being set or set it in the code as they shouldn't be defined differently. Not ideal solution.

In the meantime I was able to prevent the change coming up by just defining the server attribute as well as servers with the same value. This worked with the side effect of showing a deprecated attribute warning however this is better than having terraform reboot the VM. The ideal solution, I think, would be to remove the server attribute but obviously that introduces a, albeit small, breaking change unfortunately.

from terraform-provider-proxmox.