On 3/16/2010 10:15 PM, Michael DeHaan wrote:
Exactly, just add a "ttl-hint: 24" (hours) value to the JSON.
Hmm....
I'd saw this as something that would be a property of the fact, rather
than the output of the fact.
That is, I didn't see a need for variable timeouts.
That being said, if we do the "fact.d" for plugins, those scripts will
want to also use this mechanism,
so perhaps those /do/ speak it in JSON.
If the only interface between a fact and facter is the JSON pipe, the
TTL would have to be part of it. If it is a ruby interface, it'd
probably be some kind of accessor which too could have a code block
attached to make fancy calculations.
As alwas in IT (and elsewhere): just becaus you can (make variable
timeouts) it doesn't mean it's a good idea.
Best regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
