Struct NotifyDispatcher 

pub struct NotifyDispatcher { /* private fields */ }

The configured notify backends for one profile.

Cheap to clone behind the Arc it is always held in (Profile::notify, and the profile name -> dispatcher map handed to the relay signer backend and to NotifyJob).

Implementations

impl NotifyDispatcher

pub fn new( profile: impl Into<String>, slots: Vec<BackendSlot>, jobs: JobQueue, ) -> Self

Builds a dispatcher over already-constructed slots.

pub fn disabled(jobs: JobQueue) -> Self

A dispatcher with no backends — every dispatch is a no-op. The shape a profile with an empty notify.enabled gets, and what tests that do not care about notifications want.

pub fn profile(&self) -> &str

The profile whose [notify] section this dispatcher was built from.

pub fn slot(&self, id: &str) -> Option<&BackendSlot>

The backend registered under id, if it is still configured. None after a configuration change removed a backend a queued job still names.

pub async fn dispatch(&self, event: NotifyEvent)

Queues one delivery per backend that wants this event, and returns.

Not ?-able and with nothing useful to return: a notification can never affect the ACME response that triggered it, which is why this goes through JobQueue::enqueue_or_log — a database failure here is logged and swallowed exactly like the delivery failure it stands in for.

The delivery_id is minted per call, so the queue’s identity index never refuses a genuine second occurrence of the same event: two dispatches mean two notifications, as they always did. It is shared across the backends of one call purely so an operator can correlate them in a log.

Trait Implementations

impl Debug for NotifyDispatcher

fn fmt(&self, formatter: &mut Formatter<'_>) -> Result

dyn NotifyBackend is not Debug, so show the slot ids — the only part worth reading anyway. Mirrors FilterPolicy’s own Debug impl.