- From: Steve Bennett <
>
- To:
- Cc:
- Subject: [chef] Re: Re: How to control the order that Chef (solo) executes resources?
- Date: Mon, 9 Jul 2012 08:49:02 +1000
Hi Sascha,
Thanks for the suggestion. I tried commenting out the include_recipe that I quoted before, so:
include_recipe "build-essential"
include_recipe "mytardis::deps"
include_recipe "mytardis::nginx"
#include_recipe "mytardis::postgresql"
In this form, the build no longer does any postgresql step, and proceeds much further. So, I don't think there are any other "include_recipe postgresql" lines. Any other ideas?
Are there any workarounds that would force build-essential to run first?
Steve
On 8 July 2012 23:24, Sascha Bates
<
" target="_blank">
> 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
|
" target="_blank">
| 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
Archive powered by MHonArc 2.6.16.