On Thursday, August 8, 2013 4:48:02 AM UTC-5, mezca...@gmail.com wrote: > > In your example using hiera, you put all vhosts config data in one yaml > file. This solution seems to be maintainable in this case but if I use this > solution for bind::zone datas the yaml file still be very big and difficult > to maintain. > Is it possible with hiera to split this config data in multiple files > which contain each bind::zone resource for example? > > Hiera does not come with built-in support for what I think you want. It does, however, support pluggable data source back ends, and it ought to be fairly straightforward to build a custom one that handles whatever data format you prefer.
Still, I think you're being a bit inconsistent here. I don't see a big difference between splitting your zone data among multiple classes or modules as Mason suggested on one hand, and splitting them among multiple Hiera data files on the other. Your core problem is that you have big data, and nothing we can suggest will change that. So, what criteria are important to you in comparing potential solutions? Without a better idea of what you're after, we're just shooting in the dark. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
