In general I agree, and thats how I've implemented it so far (e.g. with a yaml dump) but when 50% of your facts require caching, it might be better to let facter handle it centrally in one global caching file.
cheers, Ohad On Mon, Feb 2, 2009 at 2:41 AM, Paul Lathrop <p...@tertiusfamily.net> wrote: > > I don't think that belongs in facter; it belongs in the fact itself. > > Just my .02 > > --Paul > > On Sat, Jan 31, 2009 at 11:18 PM, Sam Rowe <s...@samrowe.com> wrote: > > > > Oh and one other thing about 'facter.d' it'd be cool if there was some > > way to say that a given fact (or set of facts) is cache-able. Perhaps > > your fact is resource intensive to discover and doesn't change much. > > It'd be cool to have a built-in facility in facter that says "if you > > just booted, find out this fact, otherwise use the old answer." > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
