isoloom-plan 0.11.0

The target-neutral plan of a lab: the spec lowered per target, the environment a backend renders, its checks and requirements.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

//! The configuration model resolved (PLAN §3, design `plan/phase4/design.md` §1–§3): what a
//! machine's recipe is once its OS, its ports and the daemon table have been read, with nothing
//! left to resolve. The CM renderers (`isoloom-render::configure`: the shell and PowerShell libraries, the
//! Dockerfile, cloud-init, Ansible) render a [`Recipe`]; they never read the authored steps.
//!
//! - [`recipe`]: a machine's steps resolved for its family ([`Family`]), or the steps the family
//!   can't carry at all ([`Unportable`]: a repository on Windows, a Windows file's ACL).
//! - [`ContainerProcess`]: what its container runs (design §3), or why it can't ([`NoProcess`]).
//! - [`DaemonTable`]: the daemons' units and foreground forms; [`unstarted`]: the daemons a
//!   recipe installs and no step starts.
//! - [`fill`]: a template's placeholders filled in for one machine on one target.
//! - [`Configure`] and [`Handoff`]: the CM tools, each target's default, and how the infrastructure tool
//!   reaches the rendered configuration.
//!
//! All of it is pure: no I/O, no clock, no environment.

mod daemons;
mod family;
mod process;
mod recipe;
mod resources;
mod template;
mod tools;
mod unstarted;

pub use daemons::{Daemon, DaemonEntry, DaemonTable, FamilyDaemon, LogLink, Stream};
pub use family::{Family, codename};
pub use process::{ContainerProcess, NoProcess};
pub use recipe::{Recipe, Unportable, recipe};
pub use resources::{
    CommandPlan, CopyPlan, FilePlan, GroupPlan, PinnedPackage, PortSpec, RepositoryKind, RepositoryPlan, Resource, RunPlan, ServicePlan, ServiceSource, Shell,
    TemplatePlan, UserPlan,
};
pub use template::{Context, fill};
pub use tools::{Configure, Handoff, OutPath};
pub use unstarted::{Unstarted, unstarted};