Struct BackendSlot 

pub struct BackendSlot { /* private fields */ }

One configured backend, under the id a queued job addresses it by.

The id is not NotifyBackend::name: that is a &'static str a backend type answers, so every custom entry reports "custom" and two of them would be indistinguishable to a job row. It is built from the configuration instead — email, webhook:<entry>, custom:<entry> — which makes it stable across a restart, the property a durable payload needs. The same reasoning gives filter::custom its ACME_FILTER_CHECK_NAME.

Implementations

impl BackendSlot

pub fn id(&self) -> &str

The id a job payload names this backend by.

pub fn wants(&self, event: &NotifyEvent) -> bool

Whether this backend’s events list admits event.

pub fn new( id: impl Into<String>, backend: Arc<dyn NotifyBackend>, events: &[String], ) -> Self

Builds a slot directly.

from_config is how one is normally made — it derives the ids from the configuration, which is what keeps them stable across a restart. This is for a caller assembling a dispatcher over a backend of its own, which in practice means a test.