[chef] Re: Re: sending notifications to resources that don't exist yet

["Leo Dirac (SR)" < >]

Andrea, I deeply appreciate the work you put into maintaining the critical application cookbook.  But I'm hesitant to add another dependency if I can avoid it.  Especially one that makes my stack traces harder to read.

Peter's suggestion worked for me, but I'm confused by it.  If I don't use the :immediately timing option on notifies, it doesn't work.  I see in the log "Processing supervisor_service[srapiworker] action restart" followed by a debug log line from the provider, but nothing happens.  If I use :immediately the same log line is followed by the service actually restarting through the provider's execute command.  This doesn't make any sense to me.

Why is the :immediately needed to prevent the messages becoming no-ops?

On Wed, Oct 24, 2012 at 12:09 AM, Andrea Campi < " target="_blank"> > wrote:

On Wed, Oct 24, 2012 at 1:57 AM, Leo Dirac (SR) < " target="_blank"> > wrote:

I tried defining the template inside the application's before_deploy callback, but that doesn't seem to do anything.  This kind of circular dependency problem has to have a standard solution, right?

You got other answers that are very good when you're using basic Chef resources.

Since you're using the application cookbook, you have other options.

The before_deploy callback is the best pick if you want your template to change at any time, even if you are not deploying a new version of the app.

However it's broken at the moment due to http://tickets.opscode.com/browse/CHEF-3493

I am looking for a workaround I can apply in the cookbook while the underlying Chef bug is addressed.

Could you possibly revert to 10.12 while we work on this? I should have an update in the next week or so.

Andrea