ironflow-engine 2.9.0

//! Event-driven notification system for the ironflow lifecycle.
//!
//! Uses a publisher/subscriber pattern: the [`EventPublisher`] broadcasts
//! [`Event`]s to registered [`EventSubscriber`]s. Event type filtering
//! is handled by the publisher at subscription time -- subscribers only
//! receive events they signed up for.
//!
//! Built-in subscribers:
//! - [`WebhookSubscriber`] -- POSTs JSON to a URL with retry and exponential backoff.
//! - [`BetterStackSubscriber`] -- forwards error events to BetterStack Logs.
//!
//! # Architecture
//!
//! - [`Event`] -- domain event enum covering runs, steps, approvals, auth.
//! - [`EventSubscriber`] -- trait: receives and handles a single event.
//! - [`EventPublisher`] -- holds subscriptions (subscriber + event type filter),
//!   dispatches matching events via `tokio::spawn`.
//! - [`MessageFormatter`] -- trait: converts events into platform-specific messages.
//! - [`RetryConfig`] -- shared retry/backoff configuration for HTTP subscribers.
//! - [`WebhookSubscriber`] -- built-in HTTP POST implementation.
//!
//! # Examples
//!
//! ```no_run
//! use ironflow_engine::notify::{Event, EventPublisher, WebhookSubscriber};
//!
//! let mut publisher = EventPublisher::new();
//! publisher.subscribe(
//!     WebhookSubscriber::new("https://hooks.example.com/events"),
//!     &[Event::RUN_STATUS_CHANGED, Event::STEP_FAILED],
//! );
//! ```

mod betterstack;
mod event;
mod formatter;
mod publisher;
mod retry;
mod subscriber;
mod webhook;

pub use betterstack::BetterStackSubscriber;
pub use event::Event;
pub use formatter::{FormattedMessage, MessageFormatter};
pub use publisher::EventPublisher;
pub use retry::{RetryConfig, deliver_with_retry, is_accepted_202, is_success_2xx};
pub use subscriber::{EventSubscriber, SubscriberFuture};
pub use webhook::WebhookSubscriber;