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
deploy 2 vms managed by same state file vm1 with destroy_cloud_config_vdi_after_boot=true and vm2 with destroy_cloud_config_vdi_after_boot=false both have power_state=running
manually shutdown the vm1 add power_state, destroy_cloud_config_vdi_after_boot to lifecycle ignore list
rerun the plan
this produces a error │ Error: power_state must be `Running` when destroy_cloud_config_vdi_after_boot set to `true` │ │ with module.vm["vm1"].xenorchestra_vm.vm, │ on ../modules/xoa/vm/main.tf line 5, in resource "xenorchestra_vm" "vm": │ 5: resource "xenorchestra_vm" "vm" { │ ╵
Use case: if multiple vms are in the same state file and if user wants to keep some of these vms shutdown by ignoring power_state and destroy_cloud_config_vdi_after_boot.
I can understand why power_state needs to be set to running on first boot but this shouldn't checked on subsequent runs when ignoring destroy_cloud_config_vdi_after_boot.
steps to reproduce
this produces a error
│ Error: power_state must be `Running` when destroy_cloud_config_vdi_after_boot set to `true` │ │ with module.vm["vm1"].xenorchestra_vm.vm, │ on ../modules/xoa/vm/main.tf line 5, in resource "xenorchestra_vm" "vm": │ 5: resource "xenorchestra_vm" "vm" { │ ╵
Use case: if multiple vms are in the same state file and if user wants to keep some of these vms shutdown by ignoring power_state and destroy_cloud_config_vdi_after_boot.
I can understand why power_state needs to be set to running on first boot but this shouldn't checked on subsequent runs when ignoring destroy_cloud_config_vdi_after_boot.
module.tf
vm.tf
The text was updated successfully, but these errors were encountered: