On 17 August 2010 21:27, Nigel Kersten <nig...@google.com> wrote: > On Tue, Aug 17, 2010 at 1:03 PM, Jeff McCune <j...@puppetlabs.com> wrote: >> On Tue, Aug 17, 2010 at 12:31 PM, Nigel Kersten <nig...@google.com> wrote: >>> I've implemented local caching for my computational expensive and >>> infrequently varying facts, and I've been thinking about whether it >>> would make sense for Facter to implement something similar. >> >> Very cool. >> >>> I'm thinking about an easy mechanism a la :confine for declaring that >>> a given fact should be cached and has an expiry value (perhaps with >>> some simple options like cache-once-per-reboot). >> >> +1, maybe file as a feature request? >> >> I anticipate a large number of facts interacting with web service >> API's in the future, and this would be really useful for that class of >> use case. > > There are a bunch of surrounding questions about Puppet interaction > with Facter, as I can imagine you may wish to have the --test option > for Puppet automatically ignore the cache for Facter, but we may as > well kick it off now. > > http://projects.puppetlabs.com/issues/4554
This was already something I wanted on the road map and there is an issue filed as we've discussed it before but didn't have a bug. I've closed your bug as a duplicate of 4519 Paul -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-...@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
