I see the "yaml_data" and "json_data" backends, but unfortunately, I'm not a Ruby developer and trying to mock those into a file_data backend is proving frustratingly obnoxious. Honestly, I wish a "file_data" backend was included by default as I feel there a TON of value in it's existence, but that's another topic.
Basically, from the documentation at https://docs.puppet.com/puppet/5.0/hiera_custom_data_hash.html, I am able to make a custom backend, but unable to get it to parse the directory structure properly and retrieve the entire contents of the file. If you have something that would work, I would love to get it working on my end. On Monday, August 21, 2017 at 3:14:42 PM UTC-5, Henrik Lindberg wrote: > > On 21/08/17 22:03, John Baird wrote: > > There was an old hiera 3.X hiera-file backend now owned on github by > > voxpupuli... does anyone have a working example of how to reproduce this > > in Puppet 5 with the next data_hash contexts? Puppet's documentation > > seems woefully lacking in this area. > > > > Basically, I would like to be able to serve up `/etc/hosts` file from > > hiera backend, for example. > > > That should be incredibly simple to achieve with hiera 5. > What is it that you feel is lacking in terms of documentation? > > - henrik > > > -- > > Visit my Blog "Puppet on the Edge" > http://puppet-on-the-edge.blogspot.se/ > > -- 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/9154ad28-5f52-40b9-87a6-62ba6ac89e85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
