[chef-dev] Re: Re: Re: Re: why-run requires an init script for 'service' resrouce

[Daniel DeLeo < >]

On Tuesday, January 1, 2013 at 12:32 PM, Mike wrote:

Happy New Year! 2013 is bound to be an awesome year!

First off, it's our goal that minor and patch release upgrades of Chef

should not require users to make changes to existing recipes. Therefore,

this behavior is a regression.

Has a ticket been filed for this?

I don't think so. Can you create one? 

The most expedient thing is to simply skip the checks for an init script

when the commands required for the given action are specified explicitly,

e.g., if a start and check command are given, then action :start wouldn't

require the init script to be present.

I was under the (wrong) impression that this was already the case.

The approach I assumed to make sense was that "explicit overrides

implicit/defaults", as we see in other places.

Most of the providers have evolved organically as the community finds new use cases and contributes patches to make the providers work for that use case. Unfortunately, there is some unresolved friction around this now that we've added some new concepts to providers. In the long term, we need to clarify some of the rough edges around how we use resources to model bits of the system. But in the short term, we should just "make it work."

 

I'm happy to help with this any way I can.

Patches accepted, please feel free to ask if you have questions about the new why run APIs.

-- 

Daniel DeLeo

 

-Mike