> What would you recommend to do, how would you approach the problem with > getting data out of hiera in something else than puppet? Just stick > around with Hiera 3 and an old non-hiera-5 config file? Which would > likely be feasible if hiera stays somewhat supported, which it doesn't > from my understanding?! Write your own self-supported hiera? > > > Maybe this is a bit overkill for your requirements, but this was > actually one use case for Jerakia (http://jerakia.io). Hiera 5 can use > it as a backend from your Puppet implementation, and because it runs > over an HTTP API other tools can easily hook into the same data > lookups... for example there is now an Ansible lookup plugin that can > pull the same data as Puppet. It also has a client library written in > Ruby which would hook into your script.
So are you reaching out to Hiera 5 from Jerakia to do that and how are you doing it? Are you as Hendrik suggested doing a compilation? What I saw as a big difference is the whole context/scope that Hiera 5 is aware of, for doing there lookups, which works for anything being called from puppet code, but is kinda hard for an external query that must mimick that context. best ~pete -- 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/a727bc6e-fbfa-e05a-5325-bf87c218cd12%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
