Is there a reason you wouldn't, however, just add the "include_recipe" statements to the default recipe for the LWRP cookbook then? It's not uncommon to do that even for library cookbooks iirc and it gets around (I think) the issue you're describing.On Wed, May 29, 2013 at 12:39 PM, Dorian Jaminais < " target="_blank"> > wrote:
The work flow is pretty simple : assert that installation dependencies are met, clone the repo, bundle install the needed gems.All those applications have a dedicated cookbook but as the installation process is always the same work flow, I have factorized it into a LWRP.OkayI am using a LWRP instead of a recipe because I want to deploy about 15 applications that are very similar.
I have attached my provider to this mail (which by the way is included in a cookbook named gios).
In each application's cookbook I use :
gios_installer NAME do
name NAME
repository GIT_URI
command "./bin/truc"
version "master"
action :install
endAs stated in my previous emails, using the LWRP that way will include the recipes ruby, git, base::certificate, pm-openssh::rsa and pm-openssh::known_hosts only if the LWRP is called exactly once in the run_list.
Thanks for your help2013/5/29 Daniel DeLeo < " target="_blank"> >
On Wednesday, May 29, 2013 at 9:06 AM, Dorian Jaminais wrote:
Is this a known bug ? I am doing something wrong ?If the LWRP is called more than once, it tells me that the resource has already been added to the run_list even if it has not.Indeed it appears that all recipes included in a LWRP 'run_context.include_recipe' is only really added to the run_list if the LWRP is called once during the run_list.I am still tracking down my problem and I have some news.It appears that he problem is not specific to the git cookbook.
I am failing to find any clues using my google-fu so I am turning to your expertise.
2013/5/29 Dorian Jaminais < " target="_blank"> >I have a LWRP that includes some cookbooks :Hi everyoneI am having trouble with LWRP, include_recipe and roles.
run_context.include_recipe "git"
run_context.include_recipe "internal-cookbook"
run_context.include_recipe "build-essential"This is a bit odd. Why does the LWRP do this instead of a recipe? Showing more code, log output, and explaining why you're doing things this way would help others to understand your issue better.--Daniel DeLeo--
Archive powered by MHonArc 2.6.16.