On Tue, Dec 23, 2014 at 02:12PM, Roman Shaposhnik wrote: > On Tue, Dec 23, 2014 at 12:14 AM, Konstantin Boudnik <[email protected]> wrote: > > Yeah, I am pretty sceptical about master-based setups as well. In my > > understanding, for proper functioning of such a setup the recipes should be > > machine-specific or group-specific. While in our case we don't have any > > up-front information where the recipes will be executed. Hence, our way of > > using Puppet seems to be pretty well aligned with our use cases. > > > > And getting back to topic: I take it the idea of adding Gradle's end-point > > for > > Puppet apply doesn't look too sexy, right? > > It does to me, but really -- how much work are we talking about here? Just > adding a task that wraps around what's in our README today?
Yes, pretty much. It's like having a functional README. Ok, lemme make a patch for that and we'll see if there's enough interest to commit it. Thanks, Cos
