-
Notifications
You must be signed in to change notification settings - Fork 28
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
Upgrade winrm dependency gem? #24
Comments
I get this error when trying to install
|
I've seen that elsewhere. Vagrant 1.8.3 came out yesterday but there are some bugs. Looks like from the CHANGELOG there are fixes going in: https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md
|
@lmayorga1980 Yes, I've tried Vagrant 1.8.3 and got the same error installing plugins. I'm back to 1.8.1 until the dust has settled. |
Guys, Vagrant 1.8.4 released. |
Nope :). The original issue at the top was an ask to upgrade the winrm gem that serverspec uses due to the deprecated warning. Folks chimed in with another issue - that Vagrant 1.8.3 can't install plugins. The original issue I posted above is still open and will be till vagrant-serverspec 's gems are upgraded.
|
Just tried these first steps with Vagrant 1.8.4:
Where does this warning appear? |
I think when you try to provision Windows computer. |
Yes, the warning is still there, one warning per serverspec test.
Vagrant.configure('2') do |config|
config.vm.box = 'windows_2016_tp5_docker'
config.vm.provision :serverspec do |spec|
spec.pattern = 'mini_spec.rb'
end
end
describe 'box' do
describe 'windows box' do
it 'should have a vagrant user' do
expect(user 'vagrant').to exist
end
end
describe service('VirtualBox Guest Additions Service') do
it { should be_installed }
it { should be_enabled }
it { should be_running }
it { should have_start_mode("Automatic") }
end
# check WinRM
describe port(5985) do
it { should be_listening }
end
end |
Well, look it is only warning about future changes that will be implemented in 2.0 |
My bad - yes - the warnings are displayed when testing a windows box w/ vagrant-serverspec. My other reason for the ask for upgrading winrm in this vagrant plugin was to sync up the versions w/ what Vagrant (as of 1.8.3) ships with because from their changelog information - vagrant folks made a bunch of changes to winrm use in vagrant. I'm concerned if vagrant-serverspec stays on such an old version of winrm that I might have other issues w/ Windows provisioning. Maybe not - but I just got involved w/ my team to fix some of our Puppet / Windows / Vagrant testing needs and I noticed that vagrant-serverspec still ships w/ a pretty old version of winrm. Thoughts? I can live w/ the winrm warning messages however. Thanks for the info above. |
Plugins should using same WinRM version as Vagrant. |
Hey,
Can we upgrade the backing
winrm
gem?I notice the following deprecation warnings w/ the current 1.1.1 version of
vagrant-serverspec
:Thanks!
The text was updated successfully, but these errors were encountered: