2

I'm in the process of customizing community cookbooks (cassandra and elasticsearch) for use in production. From trying to get to grips with Berkshelf I have found myself uploading changes to my wrapper cookbook recipes from within my ~/chef-repo/cookbooks/ by executing:

Berks upload -b ./Berksfile --no-ssl-verify --force

This gets past the fact that my chef server is not certified, and overcomes the "frozen" cookbooks.

I'm sure that there's a better way to upload simple changes to my chef-server, as it feels somewhat extreme to force a re-upload of the entire cookbook and all it's dependencies?

Thanks in advance for any help.

Gillespie
  • 2,228
  • 2
  • 18
  • 25

1 Answers1

8

Berks upload -b ./Berksfile --no-ssl-verify --force <my cookbook name>

That will upload just the one cookbook you want (ie, the one you changed)

Tejay Cardon
  • 4,193
  • 2
  • 16
  • 31
  • Thanks, although this feels really cumbersome after say, adding a simple attribute override. Using the chef-repo pattern with a wrapper cookbook, I can upload changes using knife upload cookbook – Gillespie Mar 24 '15 at 07:33
  • 1
    well, the `-b ./Berksfile` should be optional, as that's the default location. The force would also be unnecessary if you were versioning your cookbooks (which you should). EVERY change should be a new version. – Tejay Cardon Mar 24 '15 at 17:38
  • Ding. Thanks man, I wasn't grasping the change in workflow before - makes total sense. – Gillespie Mar 24 '15 at 17:42