On Friday, January 17, 2014 2:39:16 AM UTC-6, William Leese wrote:
>
> code wise, I guess this boils down to:
>
> @user{ 'wleese3':
>   comment => "bleh",
>   uid     => 9999,
> }
>
> User <| title == 'wleese3' |> { comment => 'blah', uid => undef }
>
> where I used to rely on uid => undef resulting in 9999 being used.
>


If that ever worked for you as you think it did then that represented a 
Puppet bug.  The behavior does not correspond to current or any historic 
behavior of which I am aware.

Declaring a resource parameter to have the pseudo-value undef is an 
affirmative expression of not declaring any value for that parameter.  
Resource parameter *overrides*, on the other hand, are more literal than 
that.  Overriding a parameter with undef is not an expression of not 
overriding that parameter at all; rather, doing so overrides the target 
resource declaration as if it had originally declared undef for the 
parameter in question.  That is, it overrides the original declaration as 
if it had not declared any value for the parameter.


John

-- 
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/7db37b50-8c0c-4a39-a4b2-779d2d7946d6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to