On Fri, Jul 12, 2013 at 2:22 AM, David Schmitt <[email protected]> wrote:
>
>>
> Usually that is handled by adding a class or variable to the group and
> checking on that.
>
> I actually tried that and ran into an issue. Here's the setup:
global ---> all hosts belong to this
|
+-------- email::master defines stuff specific to an email gateway
host
In global I defined "mailertype" as "nullhost" for all but the gateway
hosts which "mailertype" gets set to "gateway."
This causes main.cf.erb to get processed one way for nullhosts and in a
much more complicated way for gateways.
When I tried this and set my gateway hosts to be a member of email::master
I get an error in dashboard complaining about conflicted variable
definitions. What's weird is if I set the variable on the node's
properties that error does not pop up.
I suppose I could just override the variable on each of the node property
sheets, but that's not what I wanted to do...
--
Peter L. Berghold [email protected]
http://blog.berghold.net
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
