Hi,
I had a nice setup where I'd load a hash of from hiera as virtual
resources. These would be considered defaults that could be overridden
through a defined type. The defined type would allow things like homedir
and such to be overridden and the rest of the params would use the defaults
as already set when declaring the virtual resource.
Suddenly someone discovered that this no longer worked. I'm pretty sure it
did in the past though.
define userman_mw::users::virtualuser (
$tagged = undef,
$account = undef,
$email = undef,
$groups = undef,
$uid = undef,
$shell = undef,
$homedir = undef,
$homemode = undef,
$manage_homedir = undef,
$service = false,
) {
Userman_mw::Add_user <| $attribute == $value |> {
email => $email,
groups => $groups,
uid => $uid,
shell => $shell,
homedir => $homedir,
homemode => $homemode,
manage_homedir => $manage_homedir,
}
}
This a snipped version of the define that allows overriding. In the past,
when no overrides were provided, the collector seemed to interpret that as
'do not change whatever the param was initially declared as'. Now, despite
being 'undef', these variables cause the declared parameters values to be
set to nil.
--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/35922b4a-bd48-463b-9efb-ce336b6ac370%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
