Jira (PUP-2748) require => Exec does not work

[John Bollinger (JIRA)]

Title: Message Title

John Bollinger commented on an issue   Re: require => Exec does not work You have a misapprehension. "Applying" a resource involves first checking whether (and in which ways) that resource is already in sync, and then performing whatever actions, if any, are needed to bring it into sync. Resources that are already in sync automatically succeed, an which case other resources that depend on them can be applied. That is what is happening in this case. Specifically, an Exec uses its 'onlyif' parameter (and 'unless' and 'creates') to determine whether it is already in sync, not to determine whether the resource itself succeeds or fails. If an Exec has an 'onlyif' command that produces a false exit status, then the Exec is deemed already in sync, and therefore succeeds without any attempt at running its 'command'. Given the Exec's command being '/bin/true' in the example code, the dependent Notify will always be applied, regardless of any 'onlyif', 'unless', or 'creates'. This is the expected behavior. Add Comment   Puppet / PUP-2748 require => Exec does not work Puppet 3.5.1 resources types File and Notify cannot successfully require an Exec. The File or Notified are applied no matter whether the Exec is applied or not: {noformat}         exec { "test" :             path => "/bin:/sbin:/usr/bin:/usr/sbin",             command => "... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.