On Tuesday, 29 January 2013 13:58:20 UTC-5, Ti Leggett wrote: > > I include that in the module that installs the shell packages and > configures them, in my case, I call it base. In other words, the variables > should be as close to the things they affect or are affected by. Just > because every node might include base (or site) doesn't mean every variable > you'll ever want to use should be in there. That, to me, creates a messier > and more confusing dependency relationship between modules that use a > variable and what that variable ultimately affects.
If you have a module that installs and configures those shells, then great. But many systems come with those shells preinstalled, and there's nothing to manage. Perhaps shells were a bad example, since one of tcsh or bash may need to be added to an OS by puppet. What about the path to sed? That's part of the base OS for all systems I manage, but the path varies from OS to OS. It seems overly cumbersome to me to create an entire module just to assign one variable, and then repeat that for a dozen or so other variables with similar circumstances. It seems cleaner to have a single small module that contains site-wide definitions that aren't obviously tied to modules of their own. -- You received this message because you are subscribed to the Google Groups "Puppet 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 http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
