Issue #14998 has been updated by eric sorenson. Status changed from Unreviewed to Needs Decision Assignee set to Randall Hansen
Randall -- There was a giant puppet-users discussion related to this: https://groups.google.com/d/topic/puppet-users/hMOTL-LtVV4/discussion Interested to hear if you think (a) it's something to spend engineering time on and (b) if so, whether there's a way to expose the functionality with a reasonable UX. ---------------------------------------- Feature #14998: allow mode changes on files without restarting the service. https://projects.puppetlabs.com/issues/14998#change-68883 Author: Jo Rhett Status: Needs Decision Priority: Normal Assignee: Randall Hansen Category: service Target version: Affected Puppet version: 2.7.14 Keywords: Branch: I managed to have a booboo tonight by restarting a process which really shouldn't be. What I ran into was that a mode change caused subscribe to fire and the process to restart. Also given that "replace" only affects file contents, this means that you can never, ever change the mode of a file for new installs only, either. So it's always a risk of restarting a process. I think it's perfectly reasonable to want that subscribe/notify only fire on content changes. Also replace should maybe be expanded to also support giving other properties the same treatment perhaps? Not sure. I have thought and thought and I just can't find a situation where I think that changing the mode should cause a refresh. Owner or group in some circumstances, but not many. I think that the default should be content only, with an option to say "any attribute". RIP said: Lots of daemons ship files like accessible only by $daemon:$daemon when what we need is $daemon:$otherdaemon or maybe $daemon:$group_of_daemons. You want to notice $otherdaemon that it can now read that file etc So I think this argues that we should have an option for what changes invoke a refresh. Something like <pre> refreshon => 'content', </pre> or <pre> refreshon => ['owner','content'], </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
