Issue #3788 has been updated by Nigel Kersten. Status changed from Investigating to Rejected
This is actually how the event system is meant to work, and the use of an Exec confuses things. I was wrong above. Two different things are going on, one is the evaluation of the resource itself, the other is the action it takes upon refresh when it gets a notification event. In the case of an Exec, by default these are the same action unless you specify a refresh command. This isn't the case for other resource types that support a refresh. ---------------------------------------- Bug #3788: subscribe overrides tags https://projects.puppetlabs.com/issues/3788 Author: Alan Barrett Status: Rejected Priority: Normal Assignee: Markus Roberts Category: metaparameters Target version: Affected Puppet version: 0.25.4 Keywords: Branch: If an exec subscribes to a file, then running puppetd with "tags=file" nevertheless runs the exec. Manifest: <pre> $script = "/usr/local/bin/myscript" $config = "/usr/local/etc/myscript.conf" file { $script: source => ... } file { $config: source => ... } exec { "run myscript": command => "${script} ${config}", subscribe => [ File[$script], File[$config] ], } </pre> Command: <pre> puppetd --onetime --test --no-noop --tags=file </pre> Result: The files are installed, and the exec is run. Desired result: The files are installed and the exec is not run. -- 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.
