From d4c76d1bcf74fcf59c039808d4b4a455da38bd3a Mon Sep 17 00:00:00 2001 From: James Shubin Date: Tue, 17 Dec 2013 14:29:54 -0500 Subject: [PATCH] Do not prepend default path because it can override modules. It is common for Puppet to manage itself. If the puppet code you are deploying pushes files to /etc/puppet/modules/, then prepending this path can break deployment because it will override the module path if the deployment code is changing. There is no good reason to include this path. Puppet has built in defaults for this reason. --- plugins/provisioners/puppet/provisioner/puppet.rb | 3 --- 1 file changed, 3 deletions(-) diff --git a/plugins/provisioners/puppet/provisioner/puppet.rb b/plugins/provisioners/puppet/provisioner/puppet.rb index 068dd88a0..e62e409b5 100644 --- a/plugins/provisioners/puppet/provisioner/puppet.rb +++ b/plugins/provisioners/puppet/provisioner/puppet.rb @@ -98,9 +98,6 @@ module VagrantPlugins options = [config.options].flatten module_paths = @module_paths.map { |_, to| to } if !@module_paths.empty? - # Prepend the default module path - module_paths.unshift("/etc/puppet/modules") - # Add the command line switch to add the module path options << "--modulepath '#{module_paths.join(':')}'" end