Events - Laravel Compose

Each stack fires events as a redeploy goes through it. They carry the Stack object, and the failure event carries the step that failed and why.

Event	When
`Mozex\Compose\Events\StackRedeployingEvent`	Before anything runs, including for stacks that turn out to be disabled.
`Mozex\Compose\Events\StackSkippedEvent`	The stack or the master switch is disabled.
`Mozex\Compose\Events\StackRedeployedEvent`	`up` succeeded.
`Mozex\Compose\Events\StackRedeployFailedEvent`	The compose file couldn't be read, the env file couldn't be written, or `build` or `up` failed. `$event->step` is `compose`, `env`, `build`, or `up`. `$event->result` holds the failed `ProcessResult` for `build` and `up`, `$event->exception` the throwable for `compose` and `env`, and `$event->reason()` gives you the message either way.

A listener that tells the team when a container didn't come back:

use Mozex\Compose\Events\StackRedeployFailedEvent;

class NotifyOnFailedStack
{
    public function handle(StackRedeployFailedEvent $event): void
    {
        Notification::route('slack', config('services.slack.ops'))->notify(
            new StackFailedNotification($event->stack->name(), $event->step, $event->reason()),
        );
    }
}

The events are plain classes. Register listeners in a service provider or through Laravel's event discovery, whichever the app uses.