So 3.6.0-rc1 is out but the new caching mechanism seems pretty much useless to me without a face or method to invalidate that cache (restarting the Puppetmaster is not a good method unless there's some one to do it with a SIGHUP or USR1/2).
The only way I can see this working for most people is having a cache of unlimited and invalidating that cache at deploy time. I'm not very susceptible that 'long lived low traffic environments like production' can benefit from large cache times because when you roll out a change you want it now, not now + timeout. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/f2bbcce2-f001-4170-a69a-9502b44e6d24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
