On 10 September 2014 08:08, Daniel Siechniewicz <[email protected]> wrote:
> Hi, > > This particular hiera backend, from what I understand, is extracting > values from puppetdb "on the fly", so you don't have to put any values > in hiera yaml/json files save for a relevant puppetdb query. This > would centralize data gathering and localize it to a "data component". > Otherwise you end up with puppetdb queries within your manifests which > could be not what you want. Then again, this really depends on your > preferences. Good luck and tell us if this worked for you. > > It looks like it's designed to deal with facts and classes only. I really need something that can get data from resources (defined types). It's crappy design, but I could move *some* of the global variables defined in my type's module into facts to make those available, but I don't see a decent way to get data out of the resources, so I don't think it solves the whole problem. Thanks for the suggestion though.. this looks like it could be very useful to simplify a couple other things I've been looking at. -- 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/CAKZ22fLvPWyy4rcaiDEWq1tda777hTAf6PBAXBJKgmjS627s9Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
