Hi,
I wonder what approaches you are currently using for sharing common information
among multiple Puppet profiles:
To come up with some examples which will need to be maintained for multiple
profiles:
- HTTP proxy settings
- IP ACLs for whitelists (eg. IP of monitoring systems, trusted hosts)
- E-mail addresses for system mails (not only for /etc/aliases)
Any thoughts?
The options I currently have on the table are:
- Don’t do any abstraction and maintain multiple copies of the same information
in hiera (eg. ::profile::redsocks::proxy_url, ::profile::apt::proxy_url).
Which in more comprehensive Puppet might not scale so well.
- As Volcane suggested on IRC, use a ::data module to provide an interface for
hiera key lookups and use ::data::some_common_thing in other profiles.
- Simply use hiera calls directly in modules such as
class profile::redsocks(
$proxy_url = hiera(‘proxy_url’)
)
Which I personally dislike, as using a module provides options for
documentation and validation as well as a defined, versionable interface to
the variables.
Thanks for your feedback!
Best, Stefan.
--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/53340303-D04B-4055-A31D-2D636471BE1D%40ono.at.
For more options, visit https://groups.google.com/d/optout.
