Issue #3537 has been updated by eric sorenson. Status changed from Needs Decision to Closed
OK, thanks Micah. I'm going to mark this bug closed, because: 1. the original request for a generalized 'requireonly' or the evaluate A - pause A - evaluate B - resume A functionality is, I think everyone agreed, not a great idea 2. the discussion morphed into the as-few-as-possible `apt-get update` runs, and there's no way to get the exact functionality you're talking about in [Update 26](#note-26) in the current provider system without adding a ton of complexity. I think what you're asking for is part of #2198, because we'd need to coalesce all the non-insync resources together and perform an action before attempting to bring any of them into sync. (You can get close to this today -- a predictable 1 apt-get update per run -- without any additional complexity following the approach in [note 6](#note-6). As Micah says above, loading the mirrors should not be a huge concern.) ---------------------------------------- Feature #3537: It should be possible to trigger (exec) resources with require https://projects.puppetlabs.com/issues/3537#change-94034 * Author: Kjetil Torgrim Homme * Status: Closed * Priority: Normal * Assignee: eric sorenson * Category: metaparameters * Target version: * Affected Puppet 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:: <pre> exec { "prereq": command => "/bin/echo prereq", refreshonly => true } exec { "main": command => "/bin/echo main", onlyif => "/bin/grep foobar /etc/issue", require => Exec["prereq"] } </pre> 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
