Ugo,
That is one way to do it. However, to use the roles and profiles pattern
fully, you would `include role::base` there, which would include your base
profile classes. Additionally, you would move the sudo statements into a
profile class so that the include role is the ONLY line in the default
So if my default node looks like this:
node default {
class { 'sudo': }
sudo::conf { 'wheel':
content => '%wheel ALL=(ALL) ALL',
}
sudo::conf { 'defaults_mail_always':
content => 'Defaultsmail_always',
}
}
Do I simply insert include profile::base in
Yeah, agreed, my default node looks like:
node default {
$role=hiera('role')
include $role
}
and the lowest priority/default-est part of my hiera hierarchy has role:
role::base. other actually classified things get role set at various parts
of the hierarchy as needed.
On Tue, Oct 18, 2016
There is no magic involved in roles and profiles -- they're just classes
that get assigned to nodes based on the node's definition.
Thus, if you want a default role assigned to the default node
definition... then assign that default role to the default node definition.
On 2016-10-18 01:58
Hi,
Is there an equivalent of the default node definition when using profiles
and roles?
Thanks,
--
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
