Ah, thanks Jeff - that's a nifty way of doing it! I've been setting templatedir which appears to override the templatedir of each module which seems to work, but I can't figure a way of doing this with files - I tried an entry [modules] in fileserver.conf as a test and this seems to just be ignored in favour of the local module files/ dir. Also use of templatedir appears to be discouraged in the docs nowadays, probably with good reason.
So the 'site module' in your case would be a method of overriding generic module settings on a per-module basis. So the idea would be that your single site module provides practically all the puppet logic for your site, right? And effectively use the generic modules as libraries (as seems to make sense to me) ? With Puppet Enterprise I'm looking to avoid individual node definitions altogether (and have super-simple manifests come to that, perhaps just a site.pp) and define the nodes in PE, but use the 'groups' feature of PE to map classes to classes in the site module. I *think* this is a similar thing to what they're getting at in the PE docs but it's all very briefly mentioned so I may be getting the wrong end of the stick completely. -- 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/-/exZPZ5gHTtkJ. 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.
