Puppet will let you set fine grained file and environment timeouts, but it doesn't really work. We are deprecating the ability to set the timeout to something other than "always cache" vs "never cache" in https://github.com/puppetlabs/puppet/pull/7001. This ticket is to disallow any values other than that.
Puppet will let you set fine grained file and environment timeouts, but it doesn't really work. We are deprecating the ability to set the timeout to something other than "always cache" vs "never cache" in [https://github.com/puppetlabs/puppet/pull/7001.] This ticket is to disallow any values other than that.
Nick, it seems like using the per-environment environment.conf override abilities would help users with many short lived feature branches vs long lived branches like production. I would think users would want to set those short lived feature branches' environment_timeout to zero (either they're testing it on a box or iterating on code, but aren't using cached versions of old code) or they are in production (or a similar long lived environment like staging) and want unlimited caching managed by code-manager.
Justin Stoller we should figure out what we want to do with this soon. Either we should remove the deprecation warning, or we should remove the fine-grained control. Coremunity doesn't have enough context on the work to make this decision.
We've been talking more about environment ttls lately with the recent file-sync work. I think after this upcoming release we can look into whether the environment-ttl work will be doable in the pre-7 timeframe and if not we can remove the deprecation notice.
Talked with Nick today, and we decided that if we're going to do something for 7 on this, we should implement environment_ttl and get rid of enviornment_timeout entirely. It probably makes sense to just file a new ticket for that second part, the first part is PUP-8014. We should discuss how this work would be best split between Froyo and Josh Cooper.