Yep, agreed with all of that. There's the detail of why shareable recipes
have failed, though, and have been replaced by LWRPs. The more involved
members of the community have all come to that realization, but its come at the
cost of years of fighting with it. I don't think the failures have been enumerated
clearly so that others understand it.
On Fri Aug 22 18:54:45 2014, Adam Jacob wrote:
I look at a little differently. I think, for most people, the promise
of shareable recipes that encode policy has failed. If you make them
flexible enough to matter (apaxhe2, say) you have a very complicated
beast, when you probably only needed 20 lines of it.
I think it may well be that the having resources be the prime unit of
re-use, rather than recipes, may well be the right abstraction in the end.
Adam
On Aug 22, 2014 6:31 PM, "Lamont Granquist" < " target="_blank"><mailto: " target="_blank"> >> wrote:https://coderanger.net/arrays-__and-chef/
On Fri Aug 22 18:12:27 2014, Bráulio Bhavamitra wrote:
I still cannot get this model of "all done by a wrapper
cookbook using
LWRP". It is just simpler to read node values...
When you go down that road you eventually wind up needing two of a
thing on a server and not just one instance. Then you start
putting arrays of hashes in your attributes. Since you're now
looping over an array and firing off a lot of resources you'll
want to internally implement that problem as LWRPs anyway. Then
eventually you'll wind up wanting to merge arrays in your
attributes and you'll wind up on this page eventually:
<https://coderanger.net/arrays-and-chef/>
Its much easier to just expose the LWRPs. Then the user can use
node attributes, drive them with databags, or just statically code
them in the LWRP.
Archive powered by MHonArc 2.6.16.