Expand description
Providers that a cloud add-on delivers for a build without that
cloud compiled in, the way crate::source::ExternalFetcher serves
cloud config sources.
The base Python wheel has no cloud code. When a config names a
cloud-only transport (email over Amazon SES, say), the provider hands
the provider config and the signal, as JSON, to the sender the
opssignal[aws] add-on registered. The add-on runs the same core
code with its cloud feature on, through send_blocking.
Traits§
- External
Sender - Delivers one signal through a cloud-only transport.
provideris the provider’s name (email),config_jsonits config andsignal_jsonthe signal, both as JSON.
Functions§
- cloud_
supported - Whether this build can deliver through
cloud’s transports, natively or through a registered add-on. - register_
cloud_ sender - Registers the sender for every cloud-only transport of
cloud(aws,gcporazure). This is what an add-on package does. - send_
blocking - Delivers a signal for an add-on, on a throwaway runtime, with errors
in the form an
ExternalSenderreturns them. This is what add-on packages call to serve a send.