General discussion about Chef

[chef] Re: Re: Re: Re: Conditional execution for custom resources


Chronological Thread 
  • From: aditya nitsure < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Re: Conditional execution for custom resources
  • Date: Tue, 19 Mar 2013 13:47:04 +0000 (GMT)
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=pm67T+BzJgQK9Sb9fC05omiBlR0/fo93nbuSLnffktTbIlyV7Z8/Pd6qjA1jaa8maWBaEov/6N8CJCHvyz+L5olMevhq/nCmpHNZG0+vJ4HGHCj8UKomZiPclxWAyYPO5NShFY2Bkul645zglJSk/pqsbvpR2QjSmroHgWncyEA=;

For given scenario LWRP worked for me. Thanks!

Yeah, if some of the functionalities or features are not supported for 'definitions' and if both (LWRP & definitions) are serving same purpose then its better to depricate 'definitions'.
For new users its confusing.

Thanks,
Aditya Nitsure


From: Jesse Nelson < >
To: chef < >
Sent: Tuesday, 19 March 2013 6:22 PM
Subject: [chef] Re: Re: Re: Conditional execution for custom resources

Think this would be a great plan :) 



On Tue, Mar 19, 2013 at 5:37 AM, Andrea Campi < " target="_blank" href="mailto: "> > wrote:
On Tue, Mar 19, 2013 at 12:22 PM, Jesse Nelson < " target="_blank" href="mailto: "> > wrote:
Definitions aren't proper resources this should work as an LWRP tho.


Perhaps it's time to deprecate definitions and start deorbiting them in time for Chef 12?

Those of us who have been using Chef for a while and following the list know that they are the poor step-brothers of LWRPs, but new users are still confused and start using them, only to be told to stop.

Is there any strong argument to keeping them? I'm not aware of any good reason.

My proposal is to to:
* remove them from the documentation, or at least clearly mark them as "do not use in new code";
* have Chef 11 log a warning;
* remove them in time for Chef 12.

Thoughts?

Andrea




Archive powered by MHonArc 2.6.16.

§