On 2014-07-07 20:54, John Bollinger wrote:
On Monday, July 7, 2014 9:39:06 AM UTC-5, henrik lindberg wrote:
On 2014-07-07 15:43, John Bollinger wrote:
[...] Consider:
>
> class mymodule {
>File { group => 'example' }
> }
>
> class mymodule::example {
On Monday, July 7, 2014 9:39:06 AM UTC-5, henrik lindberg wrote:
>
> On 2014-07-07 15:43, John Bollinger wrote:
> [...] Consider:
> >
> > class mymodule {
> >File { group => 'example' }
> > }
> >
> > class mymodule::example {
> >file { '/tmp/example': owner => 'root', ensure => '
On Friday, July 4, 2014 9:42:00 AM UTC-5, henrik lindberg wrote:
>
> Next up in the quest to understand and specify how defaults work /
> should work is the support to set class parameters via the resource
> default expression.
>
> You can do this, to set defaults on classes
>
> class a
On 2014-07-07 15:43, John Bollinger wrote:
On Thursday, July 3, 2014 8:29:48 PM UTC-5, henrik lindberg wrote:
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 dynami
On Thursday, July 3, 2014 8:29:48 PM UTC-5, henrik lindberg wrote:
>
> 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 tha
