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

Newest vagrant no long requires vagrant-winrm plugin #379

Merged
merged 1 commit into from Oct 26, 2018

Conversation

tyler-ball
Copy link
Contributor

@tyler-ball tyler-ball commented Oct 9, 2018

  1. This is pending on Add winrm and upload commands hashicorp/vagrant#10263 getting merged and released
  2. We need some logic for what to do when vagrant is between 2.1.5 and 2.1.7. Between those versions vagrant does not require vagrant-winrm but it will not work because the code from Add winrm and upload commands hashicorp/vagrant#10263 is not in there

Signed-off-by: tyler-ball tball@chef.io

@@ -556,7 +556,7 @@ def verify_winrm_plugin
" Please upgrade to version 1.6 or higher from #{WEBSITE}."
end

if !winrm_plugin_installed?
if Gem::Version.new(vagrant_version) < Gem::Version.new("2.1.5") && !winrm_plugin_installed?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<= Gem::Version("2.1.5") or < Gem::Version("2.1.6")

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @chrisroberts ! I meant to message yesterday - I was testing this locally from TK and you obviously already saw this PR 😄. But it was working well for me!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrisroberts Do you have an ETA for 2.1.6 yet?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tyler-ball Next release will be 2.2.0 and we are shooting to have it wrapped up and ready to go tomorrow. If things aren't fully ready for tomorrow then it will be Tuesday next week.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to fix this check to be < 2.2.0

@sgtcoolguy
Copy link

Hey guys, looks like hashicorp/vagrant#10263 got merged. Does this mean this can be as well?

(Sorry, I'd like to get my test-kitchen/vagrant/chef nodes up to date, and this is one of the current annoyances)

@cheeseplus
Copy link
Contributor

The check itself needs to be fixed a bit but once that is done then it can be merged and released.

@tyler-ball tyler-ball force-pushed the vagrant_winrm_unecessary branch 2 times, most recently from 416b694 to 100edd4 Compare October 26, 2018 21:33
Signed-off-by: tyler-ball <tball@chef.io>
@tyler-ball tyler-ball merged commit 7e85526 into master Oct 26, 2018
@tyler-ball tyler-ball deleted the vagrant_winrm_unecessary branch October 26, 2018 21:46
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.

None yet

4 participants