I guess I hit a bit of a nomenclature issue here. By "ENC" I didn't just
mean the node_terminus script, but the whole app - i.e. "ENC" as in the
way Dashboard is an ENC...

Though your comment does remind me that Hiera can now be more than "a
directory full of YAML files"... I guess I'll start doing some research
into hiera backends, and what they can (could possibly) do for me...

Thanks
-Jason

On 01/04/2014 10:43 AM, Peter Meier wrote:
> > But as I'm starting down the road of writing *another* ENC -
> > hopefully "a good one" this time - and more and more people whose
> > advice and knowledge I've respected for years say "use Hiera", I'm
> > starting to wonder if either (a) I'm totally missing something, or
> > (b) the community is increasingly ignoring a subset of us who, in
> > fact, don't want every bit of configuration data committed to a git
> > repo and/or like web UIs for certain things and/or need to
> > manipulate that data via an API.
>
> What you need to do is to write a tool that can act as an interface
> for a datastore for your server data.
>
> Your datastore then can then be used either by an ENC or hiera (write
> your own backend, dump the data in a supported hiera format, ...).
>
> Hiera has various advantages over an ENC and all the things that you
> can do with an ENC are also possible within hiera, but not the other
> way round.
>
> Hence, if you build your interface the way that it can be used by both
> techniques you're on the safe side and very flexible (you could even
> use it in a mix mode). And actually if you think a little bit further,
> it's actually not a big thing to support both ways of handing data
> over to puppet.
>
> ~pete
>
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52C83661.7010005%40jasonantman.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to