Thanks for your response John, I appreciate you taking a quick look around to see if anyone else has already done this. I had come to the same conclusion, that if someone has already, they mostly likely haven't shared it.
You raise valid points about EL being generally pretty unsuitable as a Hiera backend. However, the project I am working on already has an Elasticsearch instance running in it, so there would be next to no performance overhead for me. It uses a web interface to write out YAML files that are fed into a Hiera for a 'puppet apply' run which configures various aspects of the system. By using Elastic instead of YAML files, I can eliminate some of the issues surrounding concurrent access, it also means backups are simplified, as I'd just need to backup ES. This arrangement would work well in a master-less, distributed setup where a centralised Elasticsearch holds the Hiera config for a number of nodes. Of course. another database would work just as well, but given that we're already using Elastic, it seems like a natural fit. Is writing a proof-of-concept Hiera backend something that someone with reasonable coding skills be able to knock out in a few hours? Cheers, Nick -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/5262cedd-0227-456f-a9c0-b4e6d9434687%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
