On Tuesday, August 14, 2012 4:14:47 PM UTC-5, Jeff McCune wrote: > > On Mon, Aug 13, 2012 at 12:36 PM, llowder <llow...@gmail.com <javascript:> > > wrote: > >> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'", >> > > You should avoid using the import statement (see > http://projects.puppetlabs.com/issues/12929). Instead, follow the > [module conventions](docs.puppetlabs.com/guides/modules.html) > > Come on, Jeff. The OP is asking specifically about the one usage pattern for 'import' that that ticket acknowledges is required to be supported. As far as I know, every Puppet configuration must choose among these alternatives:
- declare nodes directly in site.pp, and/or - declare nodes in files 'import'ed by site.pp, or - declare no nodes at all. Even sites that rely on an ENC often have at least a few node declarations. The question is about how to organize them. As to that question, I don't think there is an established best practice. My best advice is to choose an approach that makes sense, and *stick to it*. If you decide later that a different approach would be better, then change everything over (i.e. don't mix). This is all about maintainability. You need to be able to easily find the node declaration you want, and if that declaration is absent then to determine that quickly and reliably. John -- 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/-/4eIui92soVgJ. 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.
