Sorry for the delay Felix. Here's a specific example of a situation where the fact might return what I would consider useless information and I would want to revert back to a the value set previously:
On OS X you can have an active user that is at the console and owns /dev/console. If you want to gather that information it's fairly straightforward. But under certain circumstances the owner of the console is root. In that scenario I'd still want the data set on the fact prior to that to persist. My thinking is that I can just validate the data returned (within the plugin itself) and if it doesn't meet my criteria, I can set the fact to itself using Facter.value(console_user). On Fri, Aug 29, 2014 at 9:04 AM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 08/28/2014 11:01 PM, Khoury Brazil wrote: > > I currently have it written to reuse the data using Facter.value() after > > validation but wanted to make sure there wasn't something standardized > > that I missed. > > Can you provide an example of that? I don't really see what you did there. > > -- > 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 puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/5400A4A4.5020406%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/d/optout. > -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAAqoMCZw0S9dwhV__K9Ou12kt2uDB0txK4_X9YMsWGP38wX%3DeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
