[chef] Notifications almost but not quite :immediate ?


Chronological Thread 
  • From: Kevin Keane Subscription < >
  • To: < >
  • Subject: [chef] Notifications almost but not quite :immediate ?
  • Date: Sun, 22 Sep 2013 09:22:00 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=sendgrid.info; h=subject :from:to:mime-version:content-type:sender; q=dns; s=smtpapi; b=X fF0T/BIK1lOhfh8tQUq44bUC6jh+6ww1R+4Crzd1+qUClY/Dl9DG1D06F+flIsgm FABTFhFl0GSKlQuaiEHZ/RoTcx3bB8KwPdvtfyqq+ULhx40R4YQu5TKoSjYgsAAK qqiHUw4y8o0LeHQz33OAaL4bubQACQC8mZNuXRn+dU=

Title: Notifications almost but not quite :immediate ?
I'm wondering if there is a way to get notifications to be delayed slightly, without having to wait for the end of the run?

Here is the scenario: I add several Yum repositories using a recipe. After the repositories are added, I need to rebuild the Yum cache.

I have two options to do that:

- Send a delayed notification - but then other recipes don't get the benefit of the new repositories until the next run, and thus may break.

- Send an immediate notification - but then the cache gets rebuilt multiple times. Rebuilding the Yum cache is very expensive in terms of time and bandwidth, so I want to avoid that.

Is there a trick I can use to only cause one notification to be sent after all of the repositories have been added?

Thanks!










Archive powered by MHonArc 2.6.16.

§