From the discussion last night, I pulled out a couple of things:
- People really want the “all cookbooks to all nodes” quirk fixed.
- I really want to avoid parsing the recipes, even in a text mode, on
the server, in an attempt to discover dependencies.
I think we can solve both of these problems in the short term by doing
- Implement just enough of the Roles concept to allow for the Chef
Server to determine the proper set of cookbooks
- Extend the File and Template directory structures to allow for
per-recipe files and templates, in addition to cookbook-wide ones.
That should provide both of the things Miguel requires, and moves the
ball forward a little. Does that work for you, Miguel?
We’re going to ship 0.6.0 tomorrow, and try and stick to a two-week
release cycle after that. Fixing this (and the attribute ordering
issue) are two high priorities for 0.6.2.
Adam Jacob, CTO
T: (206) 508-4759 E: email@example.com