Looking into it now, thanks. Related question, I see a lot of modules
where an optional package is available as another class, example
include apache::ssl
would install apache and mod_ssl. With parametrized classes is it now
better to make this a parameter?
node blahblah {
class { 'apache':
ssl_package => true,
}
}
I'm just trying to do things "right" the first time.
On Jan 17, 9:59 pm, Nigel Kersten <ni...@puppetlabs.com> wrote:
> On Tue, Jan 17, 2012 at 9:33 PM, Ryan Bowlby <rbowlb...@gmail.com> wrote:
> > Thanks for the great replies Nigel. As a person currently rolling out
> > Puppet into production I'm stricken with doubt about how to best
> > represent variables in a module. It would seem to me that I need to:
>
> > 1. set default values in params.pp (based on facts, yadda yadda)
> > 2. allow those values to be overridden by global namespace variables
> > (for enc support)
> > 3. further allow parametrized class declarations to take precedence
> > over 1 and 2
>
> > Can you point me to a module that does this? Alternatively, can you
> > make a recommendation for module best practices going forward.
>
> Have you looked at Hiera yet Ryan? An awful lot of this is baked into it,
> and you may find you don't need to set these at the ENC level.
>
> --
> Nigel Kersten
> Product Manager, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
