Why does 'chef-client -o' trash my locally cached cookbooks?


#1

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?


#2

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.

On Fri, Apr 17, 2015 at 1:40 PM, Jeff Blaine jblaine@kickflop.net wrote:

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?


#3

On 4/17/2015 6:59 PM, Ranjib Dey wrote:

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.

Hi Ranjib,

Well, yeah, clearly that’s how it’s implemented currently :wink:

My question was why? Is there a real reason to trash them?

On Fri, Apr 17, 2015 at 1:40 PM, Jeff Blaine <jblaine@kickflop.net
mailto:jblaine@kickflop.net> wrote:

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?

#4

On 4/20/15 6:22 AM, Jeff Blaine wrote:

On 4/17/2015 6:59 PM, Ranjib Dey wrote:

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.
Hi Ranjib,

Well, yeah, clearly that’s how it’s implemented currently :wink:

My question was why? Is there a real reason to trash them?
In Chef 12 it doesn’t.

On Fri, Apr 17, 2015 at 1:40 PM, Jeff Blaine <jblaine@kickflop.net
mailto:jblaine@kickflop.net> wrote:

 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?