For an abandoned experiment awhile back I went to the trouble of mostly
getting an external ruby script working that used Hiera 5 as a library. I
don't know that you still want to do this, sounds like there may be other
options per the conversation in the thread, but I'll post the following
lin
> 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...
> 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 does
> 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 un
Hi all,
I have a bunch of ruby script that are munging data around, part of that
data is based out of hiera.
Until now, with hiera 3, I just required hiera in my ruby script, called
lookup with a certain scope and I got my data out of hiera.
Now looking forward to puppet not anymore shipping hie
