On Apr 8, 1:50 am, Jonathon Anderson <anderbub...@gmail.com> wrote: > 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 > athttp://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?
By whom? I'm not following why defined types present a special problem here. Your ENC can't directly declare resources of built-in types, either. All resource declarations need to be in classes when you use an ENC. I don't mean to be rude, but if your type definitions leave you wondering where or how instances should be declared, then perhaps you haven't been as good a module developer as you thought. John -- 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.
