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

Updating #1

Merged
merged 87 commits into from
Sep 19, 2014
Merged

Updating #1

merged 87 commits into from
Sep 19, 2014

Conversation

rylarson
Copy link
Owner

No description provided.

tim95030 and others added 30 commits January 14, 2014 14:23
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.
Bumps semver for new backwards compatible functionality
Updates clone.rb/get_name() to allow fqdn's as VM name
flamingbear and others added 27 commits July 7, 2014 15:30
…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 added a commit that referenced this pull request Sep 19, 2014
@rylarson rylarson merged commit 60a14a1 into rylarson:master Sep 19, 2014
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants