-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLILDIACgkQbwltcAfKi3+27gCgitWOzIViRTUAgZnwMzA+V27p rGEAoJT/AJmuPnGpD5J4q2YIdSloghhz =wb5g -----END PGP SIGNATURE----- -- 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/52C82C38.7080606%40immerda.ch. For more options, visit https://groups.google.com/groups/opt_out.