On Thu, Sep 4, 2014 at 9:26 AM, jcbollinger <[email protected]> wrote: > > > As long as you intend to perform the validation inside the fact > implementation, the fact can keep and use its own cache somewhere on the > system. > > Alternatively, the master stores the most recent set of facts provided by > each node, and it can be accessed via the REST API > <https://docs.puppetlabs.com/guides/rest_api.html#facts>. You could > conceivably use that as a fact cache. >
It sounds like a local cache is my best bet. It looks like the puppet labs blog covers this: http://puppetlabs.com/blog/facter-part-3-caching-and-ttl > > Overall, however, it is probably a poor idea to compute or rely on node > facts that reflect the dynamic state of the system, as opposed to its > (semi-) stable configuration. > I absolutely agree. Facts like this would only be used for reporting purposes. Depending on transient states like that for actual application of configuration seems fragile at best. -- Khoury > > John > > -- 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/CAAqoMCYwg5BNQnFVL8jk0dy%3DgHE3oEiwOVK1k7BEqQQhtKbyjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
