[chef] Re: Re: Re: How to control the order that Chef (solo) executes resources?

[Jamie Winsor < >]

I actually would not define a role to build up the state of what your 
application server looks like. 

Not only will this not solve your problem, it also introduces coupling issues 
between your cookbooks and your chef-repo. 

Because roles are stored in your chef-repo and not distributed with your 
cookbooks, you should keep the logic of what all makes up your application 
server in a recipe in your applications cookbook. Later, you should include 
this recipe in a role or directly on the run_list. 

A common reason that resources are seemingly run out of order are when you 
explicitly request they are run at compile time. You should check to see if 
any of your recipes are attempting this. 

Jamie Winsor
@resetexistence

On Jul 8, 2012, at 6:28 AM, Mike 
<
 >
 wrote:

> Also, consider defining a role to contain a run list.
> http://wiki.opscode.com/display/chef/Roles
> http://vagrantup.com/v1/docs/provisioners/chef_solo.html#Roles
> 
> On Sun, Jul 8, 2012 at 9:24 AM, Sascha Bates 
> <
 >
>  wrote:
>> This is your culprit:
>> 
>> [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe postgresql::client
>> via include_recipe <-
>> 
>> Something has postgres as an include, probably at the top.
>> 
>> Sascha Bates
>> | 
>> 
 
>>  | 612 850 0444 | 
>> 
 
>>  |
>> 
 
>>  |
>> 
>> 
>> On 7/8/12 7:24 AM, Steve Bennett wrote:
>> 
>> [Sun, 08 Jul 2012 05:14:33 +0200] DEBUG: Loading Recipe postgresql::client
>> via include_recipe