Issue #3537 has been updated by micah -.
> 1. if any package is specified to be present and isn't, then apt-get update > 2. if any package is specified to be a particular version and there's an > older installed version, then apt-get update > 3. if any package is specified to be ensure=>latest, then apt-get update > > It's that last one that gets me. Some questions for the watchers: What is it about #3 that is problematic? > * are you (micah, alex hewson, etc) specifying every version for every > package? No, I have a mixture of settings, both versions and just installing it. > * Do you do `ensure=>latest` anywhere? Yes. > * There are a couple of comments about the load on mirrors; is it really that > bad? (Not snark, I honestly don't know, I come from a redhat background and > have had thousands of servers hitting metadata on repository servers at 30 > minute intervals without negative affect, but that is only 3 files with > if-modified-since headers so perhaps its much worse on apt servers) I'm a Debian Developer, and I dont think it is such a big deal. However, I dont know why people would be thinking that this would increase the load on the mirrors. It seems to me that if an apt-get update were to be done for any of those three conditions, I would think that the apt-get update run would be scheduled to run for that puppet run, not for each package that is installed. In otherwords, it seems sufficient to me to have 5 different package resources, satisfying any of those three conditions you outlined above, each notifying an apt-get update resource that would then run one time before doing those operations. For my purposes, doing an apt-get update run 5 different times in that example is overkill (and really slows down manifest application). micah ---------------------------------------- Feature #3537: It should be possible to trigger (exec) resources with require https://projects.puppetlabs.com/issues/3537#change-91333 * Author: Kjetil Torgrim Homme * Status: Needs Decision * 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
