Issue #17246 has been updated by eric sorenson. Status changed from Unreviewed to Needs Decision Assignee set to Andrew Parker
Andy -- care to opine on this? ---------------------------------------- Refactor #17246: Refactor Puppet::Util::Feature.add to expose caching options https://projects.puppetlabs.com/issues/17246#change-77801 Author: Dominic Cleal Status: Needs Decision Priority: Normal Assignee: Andrew Parker Category: Target version: Affected Puppet version: 3.0.0 Keywords: features Branch: The "add" method of Puppet::Util::Feature has a couple of different caching behaviours, which should instead be explicitly exposed through the options hash or via multiple methods. Prior to #14822: * blocks get immediately run and the result cached * test results get cached on the first query to the feature After #14822: * blocks get immediately run and the result cached * tests, positive results get cached on the first query to the feature The interface should probably offer the ability to always cache, positive or negative cache and to never cache. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
