Add default pathing fixes for windows provisioner and verifier #1131
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.
This patch should resolve behavior differences with both provisioners and verifiers for windows machines.
This is likely to resolve the following issue:
chef-long_script.ps1
giving error when trying to spin up windows box #1013And, although not the primary issue, another example of the incorrect pathing is shown here:
Yaml output below, with pathing issues commented.
Keys:
provisioner.chef_client_path
provisioner.ruby_bindir
Finally; here is the diagnose run with the patch:
> kitchen diagnose 2012