Skip to main content

Module apply

Module apply 

Source
Expand description

Write one rendered candidate into a target, directly.

Everything is decided before the first byte moves: every destination is checked for containment, every whole file this tool would own is checked for attribution, and the target lock is taken for the whole run. Then each destination is replaced in its own directory, and the record is written last.

There is no journal and no rollback. A run that stops leaves whole files, the previous record, a visible Git diff, and a command that runs again. What it finished is reported, because that is what the operator needs and what the next run reconciles against.

Structs§

Departures
What a landing does with every managed destination the record names and the candidate no longer lands.
Outcome
What one landing did.
Recorded
What the target’s own record says this tool owns today.

Functions§

departures
Sort every managed destination the record holds that this release no longer lands into the retired and the dropped.
departures_from
departures, where the caller holds the paths a candidate lands rather than the candidate, as a stage does.
land
Write the candidate into the target, and record it last.
refused_package_line
The line that names one refused package folder.
refused_skill_packages
Every skill package folder the landing must leave alone, as <root>/<name>/.
vouches
Whether the record vouches for the bytes one destination holds.