[chef] Re: Re: Feature test vs platform test

[Gregory Patmore < >]

There's a few stacks out there that have installed upstart, but still have the init setup installed. 

To frame the discussion some, I'm trying to adjust the application_nodejs cookbook to remove the hard dependancy on ubuntu+upstart

I've been researching, and so far I'm thinking that maybe the node["chef_client"]["init_style"] variable may be my best bet?
I'm not too familiar with the chef_client object from the recipe perspective, so unless someone can point me somewhere, I'd have to test the behavior from within an LWRP.  

To be fair, the cookbook worked for me anyway on Centos 6.3, but without the upstart configuration file getting dropped off. I just don't want anyone to rely on all the features being executed as expected so I'm trying to implement a branching in the provider that adheres to the original functionality but branches for non-upstart installations.

 

On Tue, Jan 28, 2014 at 1:30 PM, Noah Kantrowitz < " target="_blank"> > wrote:

if File.exists?('/etc/init') maybe?

--Noah

On Jan 28, 2014, at 8:52 AM, Gregory Patmore < "> > wrote:

> Hi all,
>
> I was wondering if there was any recommended way to feature test for upstart vs SysV init.  I've seen the examples of branching on platform, but in our hybrid environment we have versions of debian that use init, and some that use upstart, so platform branching isn't specific enough for me.
>
>
> Thanks for any info/advice you can provide.