Jira (PUP-2520) Need ability to invalidate the cache for environments

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Need ability to invalidate the cache for environments it could also be made to work in addition to the timeout. it stats the env's directory with filetimeout semantics, and if changed marks the env as timed out. A setting could control if that is on or off. It could be made an individual setting per environment (in its conf). Then there needs to be a mechanism to manually trigger an environment that should change configuration. That requires yet something else to watch. It is probably not a good idea to watch the directories on the environmentpath (it would invalidate caches if environments are added or removed). A special file in each such directory would need to be used. Just ideas for anyone that takes a stab at this... Add Comment   Puppet / PUP-2520 Need ability to invalidate the cache for environments Since the introduction of the new caching system for directory environments, a common request has been to add the ability to invalidate the cache of a particular environment. This would be a new value for the {{environment_timeout}} setting of {{manual}}, which would be a lot like the {{infinite}} value, but would add a watch to the environment's director... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.