Jira (PUP-1054) Services should support 'reload' in addition to 'restart'

[Thomas Kishel (JIRA)]

Title: Message Title

Thomas Kishel commented on PUP-1054   Re: Services should support 'reload' in addition to 'restart' Yes, the restart parameter workaround limits Notify/Subscribe to only perform a reload since, like in Highlander, "There can be only one" response to a refresh event. But it seems outside the scope of the Service resource to differentiate between changes to a service's configuration that require a restart vs changes that only require a reload. Adding a hasreload parameter (and reload) to the Service resource, and modifying the notify / subscribe metaparameters to handle multiple parameters would allow this: service {'example': hasreload => true, }   file {'/etc/example.conf': ensure => 'file', content => 'xxx=yyy', notify => {resource => Service['example'], event=> 'reload'}, } But doing so just for Service resources doesn't seem orthogonal, if I'm using that word correctly. Using a Exec resource with refreshonly to execute a reload seems reasonable. Wrapping that Exec in a class/module to handle variations in operating systems and their service providers would be even better. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.