On Thu, May 1, 2014 at 11:24 AM, Joachim Thuau <goo...@korigan.net> wrote:
> > > On Tuesday, April 22, 2014 6:41:18 AM UTC-7, Trevor Vaughan wrote: >> >> The more I read all of this, the more I'm a fan of a MANUAL mode. >> >> Cool. I'm coming around to the viewpoint that we are going to have to support this, but it isn't going to be part of the 3.6.0 release. Unfortunately because of other commitments we have for the 3.7 and 4.0 releases I'm not sure we'll get to it then either. However adding it in shouldn't be too difficult, so if anyone wants to take a stab at it, please do. > A file per environment $ENV_HEAD/clear_cache or something that, when >> touched, will cause the cache to clear for that environment. >> >> Since every environment has a directory now, just touching the environment's directory would probably work just as well. > I also like the NONE option since, as was pointed out, dev/test >> environments shouldn't be caching. >> >> The others don't interest me all that much in general. >> >> If the per environment option is used, I'd like to see an associated >> puppet option to go with it. >> >> All of the caching control is now on a per-environment basis. The new environment.conf file can specify that particular environment's environment_timeout value. So in order to get this kind of behavior would either add a new setting for the environment.conf or add a new valid value for environment_timeout. I'm thinking that adding a "manual" value to environment.conf would be doable. > # Clear the 'production' environment cache >> puppet cache clear >> >> # Clear the 'test' environment cache >> puppet cache clear --env='test' >> >> I think those commands would be easily done. You just need to list the environments, get the configuration for each one and touch the environment's directory. Right now the don't make the environment's directory available on that object in the code, AFAIK, but exposing that should be trivial. > >> > something like that could also be used with the source control system when > something gets deployed to refreshed the environment once things are > "updated" (svn up && puppet env refresh or whatever)... > > Yes. The way of doing this without a manual refresh is to send a graceful restart to the master's container. > if someone is just starting, just have a way to disable caching > altogether, so you can quickly iterate on your 3 test machines + > puppetmaster, and those of us who have large scale puppet masters can use > that mechanism when we deploy new modules/config for puppet. > > I'd like to have both clear specific env cache, as well as "clear > everything" (although, i would think a "clear all caches" would be > sufficient at first,... > > my $0.02 > Jok > > -- > 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/45883229-eaac-42ba-9c5b-15cb886924b1%40googlegroups.com<https://groups.google.com/d/msgid/puppet-dev/45883229-eaac-42ba-9c5b-15cb886924b1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September 22-24 in San Francisco* *Register by May 30th to take advantage of the Early Adopter discount <http://links.puppetlabs.com/puppetconf-early-adopter> **—**save $349!* -- 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/CANhgQXuD-gsfXpW5q62rTWyS1jpVwYpd3joQLdc4FqtD9Bquzw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
