Hello, We're leaning towards a small change in the behavior of how puppet finds its config files for puppet 3.x.
Here is the situation: the current mechanism that we use (assuming the config file is not explicitly specified on the command line) is a little convoluted, and involves the value of "run_mode". Roughly, what we do is to use "/etc/puppet" if the run mode is :master, and "~/.puppet" if the run mode is anything else. However, to achieve our goal of allowing apps/faces to be delivered to agent nodes via pluginsync, we need to be able to parse the config file *before we know the run_mode*. This means that we must be able to resolve the default location without taking the run mode into account. After discussing various options, the current proposal is this: 1) Look for /etc/puppet/puppet.conf. If it exists, load it. 2) If the user is not 'root', then we additionally look for ~/.puppet/puppet.conf. If it exists, we load it as well. If there are any settings that are defined in both files, the values in the user's home dir take precedence. Run mode would no longer have any bearing on where we look for config files. Thoughts? Concerns? Awesome ideas that we didn't think of? -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
