> There are however several use cases where people want to be able to > instantiate "a hiera" with a hierarchy of their own to do lookups. There > is the beginnings of such an API in puppet, but it is not well > documented and needs a bit more work.
And example, like the one I sent, would totally be enough documentation for me. (and a stable API ;) ) > In your case, do you want exactly the same as what a puppet compilation > would see (and support env, module data etc.) or do you need the > functionality of having your own hierarchy somewhere that is not mixed > into puppet? The latter. In the context of external scripts (for me) it's not the env- or module-specific data that matters. It's the global data that matters. I would totally be fine, to replicate (part of) the hierarchy in a separate config file, without all the benefits I get from the 5.x API. This is more or less what I would do now when going to continue to use the Hiera 3 freestanding gem for my scripts. > Hiera 3, the freestanding gem will at some point no longer be supported. > It may be too early to drop it for Puppet 6, but it also depends on when > it will be released. We are currently just fixing critical problems with > the hiera 3 separate gem. This is what I got from the various announcements and so I though, when now going down the move from Hiera 3 -> Hiera 5 for my puppet setup/code I'd like to have a direction for the external scripts as well. I could also see me replicating the trivial hiera stuff I do in my own code, but I'd rather like to avoid that. ;) 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/cd17ae8e-a93f-968d-11b9-de66044ba726%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
