forked from nsidc/vagrant-vsphere
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updating #1
Merged
Merged
Updating #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shifts locale so that all sections are subsections of vsphere.
Fixes development version of vagrant to 1.4.3 (as 1.5.x breaks spec). Modifies gemspec to use later, specified versions of nokogiri and rbvmomi. I'm not 100% sure I can specify both the nokogiri and rbvmomi this way without side effects.
Restricting rbvmomi dependency to fix problem with nokogiri
Conflicts: README.md vSphere.gemspec
adding RsyncError yields more helpful error messages.
…im95030-issue-27 Conflicts: lib/vSphere/action/clone.rb
Updates Gemfile for older ruby versions.
…phere into tkak-feature-proxy-connection
Bumps semver for new backwards compatible functionality
Fixes minor typo vShpere -> vSphere
…to leth-no-error-message
…Vagrant version supports Windows guests
Updates clone.rb/get_name() to allow fqdn's as VM name
…dub-set-hostname Conflicts: lib/vSphere/action.rb
…into mikola-spb-vm-base-path Conflicts: spec/clone_spec.rb spec/spec_helper.rb
Lower-case is required by Vagrant when a box is not installed locally, and it's downloaded from a remote URL.
Lower-case provider name (vSphere=>vsphere)
The denpendency check for nokogiri was updated to allow all versions of nokogiri greater than 1.5.10 as the version bundled with vagrant is currently 1.6.x.
Switched from accepting all later versions of Nokogiri to all 1.x versions.
rylarson
pushed a commit
that referenced
this pull request
Mar 2, 2016
…-pods Use traverse instead of find when resolving storagePod paths
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.