Subject: [chef] Re: Why does 'chef-client -o' trash my locally cached cookbooks?
Date: Fri, 17 Apr 2015 15:59:24 -0700
this how its designed/implemented currently. the cookbook sync step before the chef run will ensure only the cookbooks defined in run list exist in the cache folder, rest is nuked. Try using a different folder as file_cache_path when using -o to override the run list.
Maybe this is different in later versions, we're on 11.18, but is there
a reason for "override my run list this one time" to nuke all of the
locally cached cookbooks that do not match that new one-time run list?