On Tuesday, January 21, 2014 4:58:55 PM UTC-6, Pete wrote: > > > This is a perfect use case for hiera. > If you aren't using it I would suggest setting it up. > It will allow you to setup variables exactly how you describe above. > > This will get you started. > http://docs.puppetlabs.com/hiera/1/ > >
Indeed, hiera is just the ticket for feeding data to Puppet to inform it about details of each target node. It's architecture is based on a priority hierarchy of data, so hiera makes it easy to, say, define a general base configuration, override some bits of that based on which group each node belongs to, and override the same or other bits on a per-node basis. That could be perfect for populating a config file template. If the OP insists that Puppet must avoid clobbering changes applied to nodes directly via Sugar's user interface, however, then that's not really a data problem. Hiera cannot help with that part, unless by facilitating the removal of that requirement. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b2a696c2-b631-4835-a8c4-e4e7358c5850%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
