[chef] Re: Re: Re: Cookbook versions on node

[KC Braunschweig < >]

Interested to hear if people have a way to do this, but what I've
heard people do is instead have a post-commit hook on your revision
control that pushes to the server in only the ways you want and then
prevent people from uploading to the server manually to force them
through revision control and thus your other limitations.

KC

On Tue, Feb 7, 2012 at 6:52 PM, Peter Donald 
<
 >
 wrote:
> Hi,
>
> I guess I wasn't exactly clear :)
>
> On Wed, Feb 8, 2012 at 1:41 PM, AJ Christensen 
> <
 >
>  wrote:
>> Why don't you use environments built in cookbook version locking for
>
> We do this to a small degree atm but want to do it across the board.
>
> Each environment should lock the cookbooks to a particular version.
> Each environment (with the exception? of development) should only
> reference frozen cookbooks.
>
>> this, instead of trying to do it from a recipe?
>
> What I want to do from the recipe is enforce that the above rules are
> followed. I have a recipe that runs at the start of every run that
> checks some assumptions. If any of these assumptions fail  the the
> chef run aborts.
>
> --
> Cheers,
>
> Peter Donald