On Jun 15, 2012, at 10:00 AM, Ashley Penney wrote: > Like most other posters so far I think that this would be such a fundamental > change that it should come in a major version if anything. I wouldn't be > opposed to the idea of being able to filter on parameters when doing a > subscribe/notify, maybe a filter meta-parameter along the line of filter => > ['source', 'owner' ], but like most people I feel this adds a lot of > complexity for very little gain. I would prefer to simply schedule the > puppet run that changes the mode > and causes a service restart to occur out of hours and take the restart > downtime. I feel it keeps things simple to retain the existing concept of > notify.
Not all things can be restarted after they are operating. Some things need to be initialized restarted, and then never restarted again unless there is a good reason (like a configuration change). Saying "oh just restart it anyway makes no sense". Why have refreshonly => true if that was so? But your main argument is: > but like most people I feel this adds a lot of complexity for very little > gain. It's an odd phenomena, in that this wouldn't affect anyone not using the filter at all, but because they don't see a need for it they will object to someone else having the functionality. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
