Chef point to local recipe dependency

Question

I have 2 cookbooks, A and and B, where A includes recipe B. Normally, recipes are pulled from the chef server, however, I want to make a change to cookbook B, and ensure that change does not break recipe A before pushing the changes to cookbook B to the Chef Server.

How to I specify in my metadata.rb file of cookbook A that I want to use my local cookbook B, as opposed to one that is on the server?

Have you considered using test kitchen or vagrant to test cookbooks? Berkshelf is a tool for managing cookbook versions. — Mark O'Connor, Mar 10 '15 at 16:04

score 1 · Answer 1 · answered Mar 10 '15 at 18:42

I appeared to have been looking in the wrong place, the metadata.rb was not the place where I should have been making this change, it should have been in the Berksfile.

The the following line added to the end of the Berksfile solvede the problem:

cookbook "B", path: '/path/to/cookbook/B'

Chef point to local recipe dependency

1 Answers1