My only objection is that mixes up the configuration data with the Puppet code, making things less modular/portable.
I have set up a collection of parameterized classes such that all the server-unique info is in /etc/puppet/manifests/nodes/ in various <whatever>-node.pp files. I hope to transition to hiera to further separate the configuration data and Puppet code. http://puppetlabs.com/blog/the-problem-with-separating-data-from-puppet-code/ “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) ----- Josh <[email protected]> wrote: > This is more of a style question than implementation. I have a bunch of > nodes running the same software but in many cases they need config files > that are customized for that specific node. I was thinking I could push all > the main files from the app through a central class and have separate > classes for each individual node that has the config files. Is this the > best way to do this or does it go against the purpose of using puppet? > > Also, for implementation, is it best practice to create a separate module > and class for each node where the class includes only that module? Thanks. > > Josh > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/nfC30zTpr1oJ. > 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-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
