Re: [Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

2016-06-20 Thread Anderson Mills
I believe moduledir should be set in the Puppetfile, not in r10k.yaml. (Or was that a mistype?) https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#moduledir On Friday, June 17, 2016 at 3:15:28 PM UTC-7, Michael Watters wrote: > > I actually take the opposite approach. Modules

Re: [Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

2016-06-17 Thread Michael Watters
I actually take the opposite approach. Modules from the forge go in a directory named "forge_modules" and r10k will leave anything located in modules alone. From r10k.yaml: forge 'http://forge.puppetlabs.com' moduledir 'forge_modules' On Friday, June 17, 2016 at 5:28:42 PM UTC-4, Rob

Re: [Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

2016-06-17 Thread Rob Nelson
r10k will deploy the modules listed in the Puppetfile into the modules directory. If you need some local (to the controlrepo) modules that are not deployed from the Puppetfile, the recommendation is to add them to a directory called site, dist, or similar, and create a file called environment.conf

[Puppet Users] Removing unmanaged path /etc/puppetlabs/code/environments/ - r10k

2016-06-17 Thread Ali
r10k deployment is failing, if my repo paths has "modules" in it . if I change modules to any other word or even module it works fine . In order to correctly map environment on my puppet master I need r10k to map repo as /etc/puppetlabs/code/environments/production [branch name ] /