Open mcallaway opened 10 years ago
I also have this limitation, unfortunately i dont have much ruby knowledge nor the vsphere API...
@mcallaway, go ahead and submit the pull request so I can see the diff. IIRC, there are vSphere API compatibility reasons that the object tree is traversed.
We've discussed this issue in https://github.com/vmware/rbvmomi/pull/37
Our vcenter permission scheme prevents me from using vagrant-vsphere because of the way vim_helpers uses connection.serviceInstance.find_datacenter().
I made a fork here git@github.com:kindjal/vagrant-vsphere.git that introduces a couple new functions that remove the need to traverse the object tree.
I also add the use of target_folder and resource pools.
I don't want to issue a pull request until someone can take a look at my proposal to see if it makes sense and could be considered to merge. Would you be interested in reviewing my fork and letting me know if you are interested in this approach?