I think there's something simple I'm missing about module best practices and application to nodes.
Let's assume I've been a good module developer: I have a general-purpose module with no site- or node-specific knowledge, and it defines a number of classes (generalized with parameters, extlookup, hiera, whatever) and a few defined types. I can apply these classes--even parameterized classes--with an ENC, but, so far as I understand, I can't apply defined types directly to a node. I need a class that contains those defined types that I would then apply to the node. So what is that class? What sort of name should it have? By its very nature, it is either node- or site-specific, right? Thus far, I've used modules at `/etc/puppet/services` using an `s_` prefix, kind of like what's described at http://projects.puppetlabs.com/projects/1/wiki/Puppet_Best_Practice2, but I get the feeling that that is not actually what is intended. So what *is* intended? ~jonathon -- 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/-/ugsiW6zKehYJ. 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.
