[chef] Better workflow for actively-developed cookbooks

[Wes Morgan < >]

I have yet to find an ideal setup for this, but librarian-chef is oh so close.

When you are actively developing a cookbook (or modifying a fork, etc.), you 
need a git clone from which you can push and pull. This should be the same 
directory where knife expects to find the cookbook so things like "knife 
cookbook metadata" will work as expected (knife should arguably be less tied 
to a particular directory layout, but that's another issue).

I tried to make this work by cloning my active cookbook repos into 
vendor/cookbooks and then pointing the Cheffile at them via :path => 
'vendor/cookbooks/foo', but for some reason that copies the cookbook into the 
main cookbooks/ dir when you run librarian-chef install. Why is that? Knife 
then operates on that cookbook rather than the one in vendor/cookbooks and 
changes would need to be manually kept in sync with the git working copy. So 
that's a dead end.

The ideal scenario would be if librarian-chef could give me a cloned git repo 
from which I can push and pull (and properly isolate it from the parent repo 
in which it is operating, via submodules or something else), which is also in 
knife's cookbook path. Bonus points if it can do that from the :git => ... 
option rather than :path => ...

If there's a way to easily do this that I'm missing, I'd love to hear about 
it.

Thanks chefs!

Wes