[chef] Life cycle of a chef run


Chronological Thread 
  • From: Tim Uckun < >
  • To:
  • Subject: [chef] Life cycle of a chef run
  • Date: Thu, 22 Oct 2009 10:56:00 +1300
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Vidc0CE5pfeYTvnTw84K6w20D7k/pmOmlxovp05ylcdcPRk4tyOEXztOjWev1OScqP 2PYZ0Phd+QF6q4+cZ1mMz/5zMxLZzpZ7neUr56NP4/LElhQyEAWqes8lHQf5RJKQhB3v /kzRxdIfcIzNYNWXOK4DqWMFCWf7Qye/h7XZk=

Is there a way to wrap some code around the chef run?

I have two specific goals.

1. Catch exceptions and email them to me.
2. Send some data to my monitoring service after the run (if nothing
else just the fact that the run took place and went OK but I would
like to include other data from ohai).



Archive powered by MHonArc 2.6.16.

§