On 06/14/2012 12:39 PM, Jo Rhett wrote: >> What you're suggesting is a differentiation that has never existed in >> this context (afaik). I'm not sure I feel good about opening this door - >> I can easily see it become a gateway for lots of unintended effects to >> trip users up. > > How so? The variable would allow the user to be explicit. As it stands > now, I suspect most people would be surprised.
Maybe so, but if nothing else, current behaviour is very consistent, which I consider a very redeeming quality. One problem scenario I can see is users defining defaults for this parameter, with the usual scoping behaviors that can easily confuse (especially new) users. > I am also very disconcerted about the issues involved in setting up new > files. You can never, ever, EVER change the mode of a newly installed > file without restarting services on all existing machines. That doesn't > make any sense. I don't really understand your scenario. There is a new config file for service X. It gets installed from a package, presumably the X package itself. How are service restarts immediately after package installation problematic? -- 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.
