Issue #3537 has been updated by Kjetil Torgrim Homme. Status changed from Rejected to Re-opened
As far as I understand it, that would state the relationship in the wrong direction. There can be many "main" (e.g., via a define), but only one "prereq". With subscribe, the instances of "main" have to be listed explicitly in the "prereq". In addition, "prereq" would run *after* the "main"(s), which is kind of a showstopper, too :-) ---------------------------------------- Feature #3537: It should be possible to trigger (exec) resources with require http://projects.puppetlabs.com/issues/3537 Author: Kjetil Torgrim Homme Status: Re-opened Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: When an Exec has conditions associated with it (unless, creates, onlyif), it can be useful to be state prerequisites which are only run when the exec itself is run. Consider this simple example:: exec { "prereq": command => "/bin/echo prereq", refreshonly => true } exec { "main": command => "/bin/echo main", onlyif => "/bin/grep foobar /etc/issue", require => Exec["prereq"] } Here, the refreshonly will cause "prereq" to never run, since a require isn't enough to trigger it. Without refreshonly, it will run every time, but the desired behaviour is that "prereq" is run iff the onlyif command succeeds. Obviously the behaviour of "refreshonly => true" can't change, and I can't think of a good name for a tri-state alternative -- "refreshonly => 'requires-too'" ? "allevents" may be more workable. My prefered solution would be a new parameter "requireonly". Perhaps slightly misleading name, since "before" should trigger execution, too, but I think most people will understand that require/before are inherently intertwined. This could later be generalised into a metaparameter to work for more types, e.g. you could have a parent File which is only checked/updated/created when some other File requires it. -- 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.
