On 2014-03-07 9:40, David Schmitt wrote:
On 2014-07-02 21:55, John Bollinger wrote:
at the point where affected resources
are declared (for Lindberg-style defaults) or at the point where the
defaults themselves are declared (for Schmitt-style defaults, if I
understand that proposal correctly).
On 2014-03-07 22:57, John Bollinger wrote:
Here's another idea: how about removing resource defaults altogether?
My take on them has always been that their dynamic scope was their most
important feature. If that's going away then what's left is just a
minor piece of syntactic sugar, and keeping
On 2014-04-07 2:11, Igor Galić wrote:
Hi folks,
last week I proposed we add a function to puppetlabs-apache which
converts puppet booleans to httpd's On/Off.
https://github.com/puppetlabs/puppetlabs-apache/pull/782
of course that has no straight-forward approach, because in some
cases htt
Hi folks,
last week I proposed we add a function to puppetlabs-apache which
converts puppet booleans to httpd's On/Off.
https://github.com/puppetlabs/puppetlabs-apache/pull/782
of course that has no straight-forward approach, because in some
cases httpd will allow boolean values, as well as
Hi folks,
This week we triaged PRs for puppetlabs-apt, puppetlabs-apache,
puppetlabs-vcsrepo
puppetlabs-apt:
* Most PRs here are in limbo because they are still failing/missing tests.
* apenny merged 1.5.x
* it's time for a new release here.
puppetlabs-apache
Merged:
- Add validate and
On Jul 3, 2014, at 1:57 PM, John Bollinger wrote:
> Here's another idea: how about removing resource defaults altogether? My
> take on them has always been that their dynamic scope was their most
> important feature. If that's going away then what's left is just a minor
> piece of syntacti
Here's another idea: how about removing resource defaults altogether? My
take on them has always been that their dynamic scope was their most
important feature. If that's going away then what's left is just a minor
piece of syntactic sugar, and keeping them in that restricted form is
certain
On Thu, Jul 3, 2014 at 3:01 PM, David Schmitt wrote:
> On 2014-07-03 16:59, Rob Reynolds wrote:
>
>> but then I've yet to use puppet on windows for more than the most
>> basic things, so I might be missing important use cases that just
>> haven't surfaced over here yet.
>>
>>
>> No, I think you a
On 2014-07-03 16:59, Rob Reynolds wrote:
but then I've yet to use puppet on windows for more than the most
basic things, so I might be missing important use cases that just
haven't surfaced over here yet.
No, I think you are onto something. For external modules it wouldn't
be a good idea. But i
On Thu, Jul 3, 2014 at 2:25 AM, David Schmitt wrote:
> On 2014-07-02 20:15, Rob Reynolds wrote:
>
>> On Wed, Jul 2, 2014 at 7:49 AM, David Schmitt
>>
>> wrote:
>>
>> Hi Rob,
>>>
>>> The alternative would be to provide many of the well-known paths on
>>> windows as facts.
>>>
>>> file { "${::sys
On 2014-07-02 21:55, John Bollinger wrote:
at the point where affected resources
are declared (for Lindberg-style defaults) or at the point where the
defaults themselves are declared (for Schmitt-style defaults, if I
understand that proposal correctly).
My proposal would actually collapse thos
On 2014-07-02 20:15, Rob Reynolds wrote:
On Wed, Jul 2, 2014 at 7:49 AM, David Schmitt
wrote:
Hi Rob,
The alternative would be to provide many of the well-known paths on
windows as facts.
file { "${::systemdrive}/somepath/bob": ... }
Not an obvious improvement.
A different question: is %PR
12 matches
Mail list logo
