On Monday, November 12, 2012 11:46:05 AM UTC-6, Jakov Sosic wrote:
>
> On 11/08/2012 06:05 PM, Hugo Rogg wrote:
> > Meanwhile I figured out how to enable modules.
> > In my case I added this to the node's config.
> >
> > apache::mod { 'proxy_ajp': }
> >
> >
> >
> > Can't believe this is not documented or that I might have missed it.
>
> You can also do:
>
> include apache::mod::proxy_ajp, which would be a much cleaner way. The
> way you figured out is from parametrized classes and it is not the best
> way to use it. I just hope jcbollinger didn't see it because he'll get
> mad if he does :D
>
I see you've been paying attention. :-)
I haven't actually been following this thread in any detail, but I would
like to point out that
apache::mod { 'proxy_ajp': }
is the declaration of a *resource* of type 'apache::mod', named
'proxy_ajp'. Apache::mod is probably a defined type, though it could also
be a custom native type. That's not at all the same thing as
include apache::mod::proxy_ajp
which assigns a *class* named 'apache::mod::proxy_ajp' to the node. It
would be possible for the implementation of type apache::mod to make the
two statements substantially equivalent, but they are not inherently so.
Either way, no parametrized-class syntax is involved.
For the record, I have no objection to custom and defined types.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/alGGf4mthTQJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
