Hi, On 06/14/2012 03:13 PM, Jo Rhett wrote: > > Now, a few years down the road, we want to start initializing new > systems like this: > > group => myapp, > mode => 0664, > > If we set this parameter, it will modify all existing files and restart > the service on all existing hosts. This means, in essence, that I can't > use a File object to do this, I must do it with an Exec to avoid the > notify happening. This is very non-optimal. If File is so limited that > we must use Execs instead, I think we're missing the point of having a > native File type.
I don't mean to be stubborn, but I still think this is a non-issue. Puppet is not really meant to be used mainly for provisioning - it's for managing the state of system configurations. I'm aware that in the real world, there are a lot of situations when you want to modify your provisioning process, but not interfere with existing installations. But puppet is not and has never been very well suited for handling these occurences. So the "right" approach here is to ignore the mode in puppet, and adjust your provisioning process to take care of it. No, this is not very helpful advice ;-) Regards, 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.
