Giuseppe Maxia
Giuseppe Maxia
The field `power_on` is not state. It's a directive for create and update. If we want to detect state, we need to add a new field `state` (and eventually `state_text`)...
Looking at this issue from the VM standpoint: (1) VMs deployed (2) start removal (3) all VMs are powered off (4) One VM removed. The other two are needlessly powered...
> Suggested solution: >Add reference by id to each resource, maybe allow use of both, reference by name or id for a while, then deprecate reference by name: Adding support...
The compression is just used to keep several files together. If we include the directory `.terraform`, the size may also become relevant.
Related to #502
Currently, our API lack the ability of updating the name of vApp or VM. I am sure there are also other entities that need similar treatment. We have plans to...
Sorry for the extended silence. We are dealing with different priorities at the moment, and this issue has not made the cut yet.
Hi @acederlund, Currently we don't have plans to add provider VDC and storage policy resources or data sources. Regarding metadata, we want to add metadata handling to Orgs, catalogs, networks,...
> Not sure why read for power_on is not reliable. Can't you get it form status value? > e.g. > `status = 4` > ? Power status is not easy...
Hi, Thanks for the update. However, I could not reproduce your problem. First, I created an Org using your script ```hcl resource "vcd_org" "my-org" { name = "org" full_name =...