On 27 April 2010 08:52, Peter Meier wrote:
> The best practice is to either go with an external node tool for
> complexe node definitions or at least not to use any includes in
> super-nodes which behavior you want to tweak with variables in
> sub-nodes, as inheritance in nodes don't work the way
ndet: Dienstag, 27. April 2010 03:54
> An: puppet-users@googlegroups.com
> Betreff: [Puppet Users] Setting Variable in Class or Node and Using in
> Included Module
>
> Should the following approach to optionally including site-specific
> information in modules work?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [0] I have various nodes defined by function (e.g. database server) that
> inherit from a base node. One thing the base node does is check a fact
> that returns the location of the client. It then includes a module with
> the location-specific config
Should the following approach to optionally including site-specific
information in modules work? It's the third pattern documented at
http://serialized.net/2009/07/puppet-module-patterns/
In my case, I have
modules/manifests/ntp/init.pp
import "classes/*"
if ($ntp_servers) {
$servers = $ntp_s
