Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get_vm_by_uuid requires broad permissions to traverse object tree #51

Open
mcallaway opened this issue Apr 8, 2014 · 3 comments
Open

Comments

@mcallaway
Copy link

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?

@jtjeferreira
Copy link

I also have this limitation, unfortunately i dont have much ruby knowledge nor the vsphere API...

@rylarson
Copy link
Contributor

@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.

@mkuzmin
Copy link
Contributor

mkuzmin commented Jan 22, 2015

We've discussed this issue in vmware-archive/rbvmomi#37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants