From 573683ef009d50105498e365c52f6f34e09b0fdd Mon Sep 17 00:00:00 2001 From: "Paul Cooper @ Agile Barbecue" Date: Tue, 13 May 2014 17:31:31 +0100 Subject: [PATCH] fix windows guest with puppet and a facter block Powershell doesn't understand the unix-style ENV=thing command syntax, the old vagrant-windows plugin monkey patched the provisioner to put semicolons between statements to set the variables before running puppet - this fixes the issue inside a windows? block leaving the normal non-windows code path working - therefore works for me on both unix and windows provisions with a facter block in place --- plugins/provisioners/puppet/provisioner/puppet.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/provisioners/puppet/provisioner/puppet.rb b/plugins/provisioners/puppet/provisioner/puppet.rb index 79a69c2d6..c91143715 100644 --- a/plugins/provisioners/puppet/provisioner/puppet.rb +++ b/plugins/provisioners/puppet/provisioner/puppet.rb @@ -140,7 +140,7 @@ module VagrantPlugins # If we're on Windows, we need to use the PowerShell style if windows? - facts.map! { |v| "$env:#{v}" } + facts.map! { |v| "$env:#{v};" } end facter = "#{facts.join(" ")} "