[chef] Re: Re: different kind of clients, cookbook dev workflow

Adam Jacob 
<
 >
 writes:

Hi,

Thanks for your answers Adam !

> There is a feature coming in the 0.10 era Chef (0.9 is about to drop,
> and lays the foundation for this) that will let you set up multiple
> environments on a single Chef server - you can have a workstation
> environment, testing, production, etc.  Each will have the ability to
> have cookbooks pinned to particular versions, and their own roles and
> data bags.

sounds promising !
What about acl ?

>> Another question for which the answer might be related:
>> What's your developpement workflow with cookbooks ?
>
> The upcoming 0.9 release makes this easier, but mine goes like this:
>
> # If I'm adding an upstream cookbook
> $ knife cookbook site vendor COOKBOOK -d
> # Make changes
> $ edit stuff
> # Commit
> $ git commit -a -m "Did some stuff"
> # Push
> $ knife cookbook upload COOKBOOK
> # Run stuff
> $ knife ssh 'role:has_cookbook' chef-client

Ok, now let's say its recipe is in the run_list of a lot of clients.
I want to change stuff and be able to test the changes without
risking to impact the clients.
How would that be achieved with chef 0.8 ?
Clone, then put this cloned cookbook/recipe to the run_list of the
test client, change stuff, correct stuff, merge back to the cookbook
in production ?
I'm looking for a simple workflow, are there other ways ?

Would it be solved/remedied by having a way to override cookbook_path
in clients' attributes ?

-- 
Laurent