Hello,

I was reading over several threads regarding the use of concat modules and 
subscribe capabilities.  It seems everyone is subscribe from another 
resource instead of notify with a concat resource.  My preference is to use 
notify, as I think it makes the code read better for documentation 
purposes.  One thread implied that subscribe and notify are interchangeable 
as long as refreshonly=true.  Is that correct in the case of using notify 
with concat?  Is it sufficient to use one notify statement inside the main 
concat resource for a file, or do I need to notify from each 
concat::fragment resource?  I am hoping someone can clear up a bit of 
confusion I've developed reading through the threads.  

For background, I'm using puppet to configure Gnome using dconf.  I've 
written a simple Exec resource that runs dconf-update, refreshonly => true. 
 A concat resource might manage a file that collects several Gnome options 
that relate to each other, where each concat::fragment resource corresponds 
to a single Gnome option...like a fragment for enabling the screensaver, 
and another fragment for the idle-delay.  If the file is updated, 
dconf-update needs to be run and should only be run once at the end of a 
puppet run.

Thanks for your thoughts.

-- 
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/09321e9b-9161-433a-8dcc-364a27af3220%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to