Expand description
API server assembly, lifecycle, and readiness.
startup binds the TCP listener before bootstrap and serves a starting
health probe; builder composes the full axum router and global
middleware stack; runner runs the startup reconciliation, swaps the
full router onto the listener, and awaits shutdown. The readiness
signalling surface (is_ready, signal_ready, wait_for_ready) is
used by external health probes. Discovery, health, metrics, and route
configuration live in the private submodules.
Re-exports§
pub use readiness::ReadinessEvent;pub use readiness::get_readiness_receiver;pub use readiness::init_readiness;pub use readiness::is_ready;pub use readiness::signal_ready;pub use readiness::signal_shutdown;pub use readiness::wait_for_ready;pub use startup::EarlyServer;pub use startup::bind_and_serve;pub use startup::starting_router;pub use builder::*;pub use runner::*;