[chef] Re: Re: Re: Re: knife.rb cookbook_path with Berkshelf

["Mark H. Nichols" < >]

On Aug 21, 2013, at 2:34 PM, Ranjib Dey 
<
 >
 wrote:

> you can specify any valid git rev iirc (i.e. branch, sha, tag etc), since 
> berks uses the ~/.berkshelf/cookbooks as cache directory, it will store all 
> the versions that you have specified in your berksfile. 

I have successfully used branch before. However the resulting directory under 
.berkshelf/cookbooks includes the Git SHA as part of the name. Over time I've 
accumulated several versions of the same cookbook that all have different 
SHAs as a part of the directory name. What I can't figure out is how to get a 
more meaningful name created via Berkshelf when I pull the cookbook from 
Github. Having to specify `knife cookbook upload 
ome_jboss-daa338348c4d14e9e1abe693ecc98dfc6d412f5c` isn't going to be a lot 
of fun.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail