[chef] Re: Re: About Opscode's cookbook repo changes

[Miquel Torres < >]

That would be a possible solution. It is not a good one, because you
need to install the whole chef package plus dependencies to use knife,
and you even get a chef-client running, which you definitely don't
want in your desktop.

Isn't it possible to for example use a rake task, and only need to
install a chef "light" package or something?



2011/6/17 Daniel DeLeo 
<
 >:
>
> On Friday, June 17, 2011 at 2:10 AM, Miquel Torres wrote:
>
>> Hi all,
>>
>> last month there was a post regarding changes in the opscode cookbooks 
>> repo:
>> http://www.opscode.com/blog/2011/05/24/update-on-the-future-of-opscodes-cookbooks/
>>
>> While I can understand the reasons that made Opscode remove the
>> metadata.json from all cookbooks, it does pose a big problem for
>> non-ruby tools like LittleChef, which depended on JSON to
>> inter-operate.
>>
>> Is there a way to generate metadata.json for all cookbooks that
>> doesn't need a Chef Server?
>> "knife cookbook metadata" doesn't classify there, unfortunately.
>>
>> Cheers,
>> Miquel
> knife cookbook metadata doesn't need to talk to the server to work, but the 
> config checker will error out if you don't have a key. So the best solution 
> is to patch knife so that the config checker only cares about your private 
> key when running a command that requires it.
>
> --
> Dan DeLeo
>
>