This really speaks to me. I haven't dabbled in ENCs as of yet, but my natural response to the question of hiera vs. ENC would be to use the right tool for the respective job. If the added complexity of using both is acceptable, do go ahead and use both.
If I got my history correct, hiera was not intended to be an ENC alternative or replacement. It did replace extlookup, which in turn was kind of a crutch for people who didn't want to invest the effort of creating a full fledged ENC. Personally, I agree with most commentors that hiera should not be a reason to deprecate the ENC concept altogether. Cheers, Felix On 01/06/2014 10:09 AM, simon c wrote: > For myself, I can see that Hiera is really the way to go, (with a good > front end), however for where > I am now on the puppet rollout, asking other admins to create even > simple json/yaml files for > each node would not get anywhere. > > So, I've got a very simple node terminus ENC script that parses flat > text files to groups & > "roles" and anything more complex goes either goes into hiera, or into a > node specific > manifest class file. > > I quite liked the puppet dashboard as an ENC, but there was no way to > audit who > changed what when, which would be unacceptable in our environment. -- 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/52CBE036.8020203%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
