proxmox qemu resource created from cloned template results in infinate boot loop and broken configuration

[enthusedcoder]

Hello. So, I was hoping to use your proxmox terraform provider to build out our proxmox infrastructure, so I started with a light test. Below you will find the barebones terraform config file:

terraform {
  required_providers {
    proxmox = {
      source  = "Telmate/proxmox"
      version = "3.0.2-rc10"
    }
  }
}

provider "proxmox" {
  pm_api_url = "https://10.207.106.3:8006/api2/json"
  pm_api_token_id = "I have the value hard coded here.  What?!  Did you honestly expect me to just leave it in here?"
  pm_api_token_secret = "I have the value hard coded here.  What?!  Did you honestly expect me to just leave it in here?"
  pm_tls_insecure = true
  pm_log_enable = true
  pm_log_file   = "terraform-plugin-proxmox.log"
  pm_debug      = true
  pm_log_levels = {
    _default    = "debug"
    _capturelog = ""
  }
}

resource "proxmox_vm_qemu" "reg1" {
  name = "PB99996-P01-T"
  target_node = "anprox"
  clone = "POS-win11-Template"
  power_state = "running"
  pool = "res"
  full_clone = false
}

I figured that the above config would be sufficient, as the documentation for this provider states "For ISO and clone modes, the name and target node of the VM are the only required parameters." Please correct me if I am wrong, but, when I read that statement, I am led to believe that the reason no other cofiguration is required is because proxmox will just copy the configuration used in the template. Below is a snapshot of the virtual hardware menu for the template that I was attempting to create a linked clone of in my terraform config:

However, the deployed resource becomes stuck in a boot loop, and one can quickly see why: the hardware settings for the deployed resource were not copied from the clone, as you can see in the snapshot of the hardware menu of the resulting deployed resource below:

Meanwhile, terraform (but mostly your provider) is reporting that the operation was a success. Can't say that I agree. What is going on here?

[enthusedcoder]

Below I have attached the log generated when the terraform config was applied. Just a heads up, guys, the log that was output contains the authentication information in plain text, for the world to see:

I needed to take some time to go through the log and scrub that very sensitive information from the document in its entirety, but I think we can all agree that that kind of information should not be present by default in output logs that are going to be posted publically. Even now, I am hesitant to post the scrubbed log, as I am worried that some sensitive information might still be contained within, but will do so nonetheless. Below is the scrubbed log file:

terraform-plugin-proxmox.log

[Tinyblargon]

@enthusedcoder resources that should remain after the clone have to be in the Terraform config. It used to be different, but that caused a lot of issues. The documentation you mentioned is probably out of date.

As for the sensitive info, at some point the provider prints almost everything, and I agree we should change that.