On 01/17/2011 02:52 PM, Adrian Bridgett wrote:
> Hi Frank,
"Felix".
> then overridden here:
>
> class puppetserver::config inherits puppet::config{
Oops - sorry, I completely missed that inherits clause in your previous
mail. Also your override syntax. *facepalm*
>> Also note that resource defaults become mute if you assign *any*
>> parameter value in an actual instance declaration. So
>>
>> File { notify => Service["foo"] }
>> file { "baz": notify +> Service["bar"] }
>>
>> doesn't mean "enhance the default by Service["bar"]", but instead it
>> means "replace the default by whatever was set *for this very file* plus
>> Service["bar"]".
I should have added "that's what I infer and what seems sort of logical
to me."
>> As an aside, I try and steer clear of plusignment whenever it's possible.
>
> Ah, interesting - I hadn't appreciated that, it seems a bit of a shame
> in some ways. That explains what I'm seeing.
>
> One reason for the slight oddness here and setting defaults was to all
> a more standardised approach in how we write modules - to avoid
> missing notifies (or conversely too many).
I agree about exploiting resource defaults where possible, but
apparently they don't play nice with plusignment overrides, as you
noticed here.
It would be interesting to see whether repeating the notify parameter in
your file { } declaration (in redundance with the default you declare)
fixes your problem.
Cheers,
Felix
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
