On 14/06/16 18:06, Sean A wrote: > Hi, > > I'm working to get r10k to populate modules on our puppet masters. I > have this working, but there are some complications with Foreman, I'm > seeking input on. > > We make use of /etc/puppet/environments/common as part of the > basemodulepath, this is setup from the Foreman Installer, and part of > the puppet.conf template as far as I can tell. I have r10k setup to > manage this directory as well, but it wants to make > /etc/puppet/environments/common/modules and place any modules in the > Puppetfile there. This creates two stumbles for me... > > 1. Is there a way to easily override the Foreman-Installer's > puppet.conf template? ...so I can change the basemodulepath according > to my needs at install, and not have it wiped out if foreman-installer > is run again?
You could try setting --puppet-server-common-modules-path, which I think is by default set to an array of the common dir, /etc/puppet/modules and /usr/share/puppet/modules (see/grep its entry in foreman-installer --full-help or the answers file to check). To set an array with the installer, pass the argument once for each entry. > 2. Importing the environments and modules always involves ignoring the > "common" environment. Is there a way to get Foreman to always ignore > this environment? You can list ignored environments in /usr/share/foreman/config/ignored_environments.yml (copy the sample file) with: :ignored: - common -- Dominic Cleal [email protected] -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
