> 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 doesn't
> from my un
On Wed, Oct 5, 2016 at 12:24 AM, Aditya Gupta
wrote:
> Hello All,
> I am using host resources in my puppet class to manage hosts file of the
> client.
>
> I am facing one issue where if I have already connected client to the
> puppet server where hosts file have its own entries as well as entries
p and go out soon as 1.2, not 2.0.
Thanks, from me and Jeff Goldblum.
Craig
On Tue, Aug 23, 2016 at 10:00 PM, Craig Dunn wrote:
>
> Hi all
>
> I'm after a bit of advice on talking to some Puppet internals...
> background; I have a module called crayfishx/purge which so fa
Hi all
I'm after a bit of advice on talking to some Puppet internals...
background; I have a module called crayfishx/purge which so far has proved
pretty stable and useful. It works on the same principle as the resources
resource in Puppet, in so far that it spits out resources from the generate
See
# puppet help facts upload
That sounds like what you want... you may need to tweak your auth.conf
settings too.
On Thu, Aug 18, 2016 at 7:48 AM, Aditya Gupta
wrote:
> Hello All,
>
> Here is the steps of complete puppet run for client :
>
> 1. puppet client send facts to the puppet serve
On Wed, Aug 13, 2014 at 5:55 AM, Wil Cooley wrote:
>
> On Aug 12, 2014 1:00 PM, "Daniele Sluijters"
> wrote:
> >
> > Please don't use `dox`. It's like a teenager who wasn't taught enough
> English in school, or simply doesn't care, to know that the accepted plural
> of doc is docs, not dox, dawg
This is a lot nicer than the existing workarounds using ensure_resource and
defined. Previously I was thinking about something along similar lines
but with slightly different behavior. I was thinking of some mechanism
whereby if you define a constraint then it will be autorequired *if* it is
in
### Global `$facts` Hash
>
> You have to manually enable this (along with the `$trusted` hash) by on
> your puppet master(s). It'll be on by default in Puppet 4.
>
> In addition to using `$fact_name`, you can now use `$facts[fact_name]` to
> get a fact value. The `$facts` hash is protected and can
