Hello!
One thing I've noticed is that folks trying to implement something like a 'service' resource always have better luck with an HWRP where they can actually subclass a real service resource class. It seems like LWRPs that try to imitate a service-like resource almost always fall short due to limitations in notifications. Is it a best practice to prefer HWRPs that extend existing service resources and/or providers over LWRPs that try to expose service-like functionality? Cheers, - Martin
From: Ameir Abdeldayem
Sent: Wednesday, August 27, 2014 6:25 AM To: Subject: [chef] Re: Re: LWRP for N00bs While we're on the topic, what are some pros/cons to writing resources in the "libraries" directory vs "true" LWRP style in the "resources" and "providers" directories? I see that a
lot of Sean's contributions go the "libraries" route, but there's a pretty diverse mix community-wide (with most seeming to be "true" LWRP style).
-Ameir
On Wed, Aug 27, 2014 at 1:17 AM, Julian C. Dunn
<
" target="_blank">
> wrote:
The conversion logic is here: |
Archive powered by MHonArc 2.6.16.