you might want to explicitly top-scope role, ie.
$::role = 'nameserver'
Not sure if that will matter in this case, but I don't think it can hurt.
As an aside, we set our role variable with facter.d on the nodes
themselves, as we don't have hostnames that easily work out to roles.
On Wednesday, August 21, 2013 10:20:56 AM UTC-7, JeremyCampbell wrote:
>
>
> I need to define data for roles so I add the 'role' dynamic data source.
>
> - "%{::environment}/%{::clientcert}"
> - "%{::clientcert}"
> - "%{::environment}
> - "%{::role}"
> - common
>
> Our site.pp uses a hostname regex to classify nodes into roles e.g.
>
> node /^ns\d+$/ {
> include role::nameserver
> }
>
> Can we add the $role variable to the role class and hiera will use it?
> e.g.
>
> class role::nameserver {
> $role = 'nameserver'
> include base
> include bind
> include shorewall
> }
>
> Would this work? Is there a better pattern that doesn't involve having to
> define custom facts on the servers?
>
--
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.
