You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use pulumi package that is using under the hood this provider's latest version to configure the Proxmox cluster.
And i've noticed that the startup clause in qemu.conf either not supported or treated wrong.
To be specific: here is how the parameter startup looks like in qemu config file:
It was configured from a Proxmox UI here: VM/CT => Options => "Start/Shutdown Order".
Then i do a pulumi refresh that should match the real cluster state with the current state file, and got the error from provider:
* error retrieving VM: failed to decode HTTP GET response (path: nodes/pve-b2/qemu/100/config) - Reason: json: cannot unmarshal string into Go struct field GetResponseData.data.startup of type vms.CustomStartupOrder
The text was updated successfully, but these errors were encountered:
Thanks for the report. The startup order is not fully supported at the moment. It was added to the original PVE API client a while back, but was not actually exposed in the TF VM resource. I believe the API has changed a bit since then, and become incompatible with the client, so it throws an error you see.
Running Proxmox 7.4
I use pulumi package that is using under the hood this provider's latest version to configure the Proxmox cluster.
And i've noticed that the
startup
clause in qemu.conf either not supported or treated wrong.To be specific: here is how the parameter
startup
looks like in qemu config file:It was configured from a Proxmox UI here: VM/CT => Options => "Start/Shutdown Order".
Then i do a
pulumi refresh
that should match the real cluster state with the current state file, and got the error from provider:The text was updated successfully, but these errors were encountered: