On 07/16/2012 10:29 PM, Jo Rhett wrote: > We aren't, because we have no external datasource for this stuff and > every example we've seen (like yours above) indicates that we're going > to have to put half of the logic engine of puppet inside the data > source, which means it needs to be a very complex thing that enforces > the structure and somehow ties it with the puppet logic. Our analysis so > far is that to implement hiera we're going to have to write our own > software platform which manages hiera data and writes out puppet > policies on the fly when the data changes.
Not quite. I believe that the canonical approach is to move your node -> roles relation into hiera. This way you need little "individual" manifest code per node. You certainly need a means to manage hiera's datastores, but I don't think generating manifests is required. Anyway, as participants in this thread seem to agree, the approach is limited insofar that puppet has some shortcomings in the area of constructing complex derived data (e.g. groups for given users) from complex and disjoint pieces of input data. Since you're going to end up with some sort of kludge anyway (imho), I believe it's perfectly fine for you to forego the hiera backend at this time and apply the kludge inside your comfort zone, for what it's worth. Cheers, Felix -- 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.
