Most likely because that’s an easy way to show the parameters a class
supports. Some modules use hiera data to show that, though it is a bit more
complicated to explain and understand, especially for novices.
On Tue, May 21, 2019 at 9:42 AM Peter Berghold
wrote:
> Using include instead of class
Using include instead of class makes sense to me and was my instinctive
thought.
Why on earth, then, do all the (or most) of the Puppet Forge modules use
the
class{'myclass':
param1 => 'thing'
}
patterns in their examples. I had begun to believe that was the preferred
pattern.
I will mend
On 2019-05-20 18:57, Peter Berghold wrote:
So here I am I have a base profile for my Ubuntu (Debian family)
machines that invokes the class
class{'apt':
... some paramters
}
I then invoke the class
class{'postgresql': }
and now Puppet is screaming that the class 'apt' cannot be invoked
So here I am I have a base profile for my Ubuntu (Debian family) machines
that invokes the class
class{'apt':
... some paramters
}
I then invoke the class
class{'postgresql': }
and now Puppet is screaming that the class 'apt' cannot be invoked twice.
This seems to be a flaw in Puppet manif
