max / makenotwork

1.5 KB · 30 lines History Blame Raw

1	//! ops-core — shared infrastructure for operator tools (Sando, Bento).
2	//!
3	//! These are the genuinely domain-agnostic primitives that both the
4	//! tier-promotion deployer (Sando) and the app-release orchestrator (Bento)
5	//! need. Each tool keeps its own domain types (tiers/gates vs targets/steps),
6	//! recipes, and route handlers; only the transport-and-plumbing layer lives
7	//! here so there is exactly one copy.
8	//!
9	//! - [`remote`] — re-exported from the `ops-exec` crate: the streaming SSH (or
10	//! local) command primitive ([`remote::RemoteHost`]) and the
11	//! [`remote::LogSink`] sink trait. The capability-gated `Executor` trait and
12	//! its transports live in `ops-exec` proper (re-exported here as [`ops_exec`]).
13	//! - [`eventbus`] — a generic `EventEnvelope<E>` broadcast bus with flat-`kind`
14	//! serialization (each tool supplies its own concrete `Event` enum as `E`).
15	//! - [`live_log`] — a disk-append + callback live-log sink that implements
16	//! `LogSink`; parameterized over a chunk callback so it is not tied to any
17	//! tool's `Event` enum.
18	//! - [`sqlite`] — connection helper (each tool runs its own `sqlx::migrate!`).
19
20	pub mod eventbus;
21	pub mod live_log;
22	pub mod sqlite;
23
24	/// The trusted executor crate, re-exported so consumers can depend on
25	/// `ops-core` alone and get the `Executor` trait + transports transitively.
26	pub use ops_exec;
27	/// The low-level streaming primitive + `LogSink`, kept at the historical
28	/// `ops_core::remote` path so existing consumers compile unchanged.
29	pub use ops_exec::remote;
30