Use winrm v2 release gems

[mwrock]

This is a work in progress and should not be merged until winrm v2 and corresponding releases in winrm-fs and winrm-elevated are released.

This is mostly working but the following needs to happen:

• tighten up error output in winrm (its a bit much)
• convert winrm-elevated and its usage to work with v2
• get the tests passing

[mwrock]

Errors are looking good now. Working to get elevated transport functional.

[mwrock]

see WinRb/winrm-elevated#11

[mwrock]

Might be changing the shell interface for winrm-elevated

[mwrock]

Build break is now filezilla related and I'll address in a separate pr.

[mwrock]

This is no longer a work in progress. There are a couple post release items to be done here. Currently the Gemfile pins kitchen-inspec and train to their respective winrm-v2 branches. This breaks the kitchen-init cucumber feature. For now I have commented out that test and after kitchen-inspec and train release we can revert the comments in the kitchen-init test and remove the pins in the gemfile.

[mwrock]

If you want to test, this should work with any windows based cookbook. Additionally, kitchen-dsc based projects can also now converge on Windows Nano Server. If you clone https://github.com/mwrock/DSCTextfile and:

bundle install
bundle exec kitchen verify

that should create my WindowsNanoDCS vagrant box and converge/test the resource.

[mwrock]

I should mention here that we have been using this branch in the chef and chef-dk acceptance tests that test every package that drops into the current channel for the past couple months.

[cheeseplus]

+ a billion

[smurawski]

👍