-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
provider/vsphere: Standardizing datastore references to use builtin Path func #8075
Conversation
LGTM |
@stack72 After I built I got the change in internal_plugin_list.go. Looks like it just moved an entry to the top of that struct. Do you have ideas on why? I figured I'd leave it since the build consistently did this. |
Hey @dkalleg Ignore that change, that is because i merged a new provider - i will take care of that. Please can you drop in the test run output for reference and then i can merge :) Thanks! P. |
This is a fix to allow use of datastores that are part of a datastore cluster using the syntax <datastore cluster name>/<datastore name>
e7f31d4
to
5bd8fad
Compare
@stack72 Realized that the disk update test was failing in a multi datastore scenario so I had to update it. Results: VirtualDisk tests
cdrom test
Disk update test
|
Thanks for this @dkalleg :) Glad to see that the test results help find a potential issue! P. |
…rp#8075) This is a fix to allow use of datastores that are part of a datastore cluster using the syntax <datastore cluster name>/<datastore name>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This is a fix to standardizes the way datastore paths are build. This will also allow use of datastores that are part of a datastore cluster using the syntax
<datastore cluster name>/<datastore name>