On 12/18/2012 07:20 PM, Philip Brown wrote: > Hmm. Thanks for the explanation. It sounds *potentially* useful. > However, still one problem: > I dont think it's additive. > > In other words, you cant have a truly modular flow in hiera, where you have > the following pseudocode > > $(allhosts ) => gets 'classes' list from common.yaml > > $(dbmachines) => gets additional classes from dbhosts.yaml > > $(webmachines) => gets additional classes from webhosts.yaml > > > If you want a host that is both a db machine, AND a webserver, you need > to create a new hiera file, > dbandwebhost.yaml > and then make sure that all machines in that context, get pointed to > that specific file, rather than getting to merge things. > > > The only method I see that uses the "pure" hiera_include method you show > above, and still allows for mix-and-max class includes, would be to > handcraft individual > > FQDN.yaml > > files for each and every host. ?
You can write your own ENC script, which gathers all the classes from different files and makes join instead of returning first result. http://docs.puppetlabs.com/guides/external_nodes.html -- 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.
