On 08/26/2013 11:41 AM, Andy Parker wrote: > How would you handle reloading in this scenario? > > > I can think of two ways: track all of the files loaded and reload when > something changes or is added, reload only when told. I lean towards the > "reload only when told" for a production master, since then the runtime > behavior of it is much more predictable in time (no more stating) and in > catalogs produced (no more ending up with half of one manifest version > and half of another).
I think the "load everything" and "only reload when told to" approach is the correct one for the master. I suspect it will solve the random classes disappearing while pushing an update problem I've seen in the wild (but can't reproduce on demand) and definitely the fall out I see when trying to change the git branch for an entire environment. This is a very logical workflow and one many folks are already accustomed to from HUPing bind, etc. I'd advocate caution about making "greedy loading" the default for local apply. Syntastic can already be painful slow. :( -Josh -- -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
