It may not be a big issue for you, but it can be when you are on a slow Internet connection, or when you pay by the megabyte.
Our values: Privacy, Liberty, Justice
From: John Dewey firstname.lastname@example.org
Sent: Sunday 22nd September 2013 14:45
Subject: [chef] Re: Re: Notifications almost but not quite :immediate ?
Sure, I still don’t see it as that big of an issue. Happens once when the repo is added.
On Sunday, September 22, 2013 at 1:57 PM, Mike wrote:
The yum repository resource from that cookbook will execute the makecache command for each repo added, notified immediately. This is no different from the OP’s problem of getting them all to run once.
I face a similar issue with the apt cookbook.
On Sunday, September 22, 2013, John Dewey wrote:
Have you tried adding repos using the yum cookbook? This should take care of what you need.
On Sunday, September 22, 2013 at 9:22 AM, Kevin Keane Subscription wrote:
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?