[chef] Re: Re: json gem conflict

On Mon, 13 May 2013, 

 
 wrote:

> (re-adding chef list)
> 
> On Mon, 13 May 2013, Sam Darwin wrote:
> 
> > Look closely at the fog page on github for recent changes in the last
> > month which are very very similar to the error message.
>  
> Yeah, I wonder if it's this fix:
> 
> https://github.com/fog/fog/commit/f2bd2404d1882a6244afea0836614146331dab56
> 
> And I wonder how long my systems have to live with this breakage until the
> next fog release is out. Until then, I have to run chef twice at instance
> launch, which is suboptimal.
> 
> This makes me wonder how, if at all, I can manage preventing changes from
> upstream providers breaking things in my own environment. Do I start rolling
> my own gems? In this particular case, I wonder if I should specify the 
> version
> of the fog gem prior to the breakage. Probably..

Yep, that's it. Just specify a version of fog that doesn't break. Silly me.
This works:

  fog = chef_gem "fog" do
    action :nothing
    version "1.10.1"
  end
  fog.run_action( :install )