We've been discussing what the default environment_timeout setting should be. There is general agreement that the current 3 minutes is not great. It's both baffling to new users and does not bring in the full performance benefits.
Two main perspectives on this: 1. Performance should be the primary driver and that the default of unlimited (cache never automatically refreshes) is preferred. This assumes most users have a code deployment workflow and tooling which can be adjusted to include the steps required to update the cache. These steps are either hitting the puppetserver environment cache endpoint, or restarting the service to cause the cache to update. 2. New user experience should be the primary driver and that a default of 0 (caching off) is preferred. This assumes brand new users will be baffled when they create or modify puppet code on the server and do not see it take effect during their test runs. By the time users encounter performance problems they will be more familiar with puppet, and this setting will be found when they dig into tuning. This setting can be managed per environment, and I'm guessing experienced users will do so. This question is focused on the out of the box defaults. Appreciate your thoughts. Owen -- 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 puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/f524207b-9dff-4e57-a46e-08bd31c640e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
