Expand description
Offline render of declared gateway trees (Phase 21).
Invariants every deploy module keeps:
- Pure and offline. No network, no profile, no
crate::session::Session. Functions take bytes (or an injected file set) and return models. - Deterministic. Ordered collections only, no clock reads, no randomness, no dependence on directory iteration order. The same input yields the same output or the same error.
- Core never prints. Findings ride
crate::error::CoreError; the binary renders them.
Modules§
- apply
- The guarded write half of
deploy(Phase 23): gates, journal, snapshots, the apply engine and rollback. - exclude
- Excluded tag providers: gateway-owned providers no deploy verb touches.
- layout
- Path vocabulary for declared trees:
RelPath, collection paths and resource keys. - ledger
- The declared-names ledger, format v1 (Phase 22, D-05, D-07).
- lint
- Render stage 7: the fail-closed lints (Phase 21, plan 21-08, DRND-07 and DRND-08).
- manifest
manifest.yaml: the declared tree’s root file.- native_
tags - The git module’s native tag export, read from a project repo (Phase 26, D-04, D-08, TAGDEP-01).
- node
- Order-preserving JSON tree and the Gson-compatible writer (DRND-05).
- pair
- The backup node of a redundant pair, read-only (Phase 24, DPAIR-01 to DPAIR-03).
- plan
- The plan engine (Phase 22): the rendered tree against what is live.
- project_
artifact - The project artifact and its canonical digest (Phase 25, D-01, D-09).
- project_
run - The host copy of a tag-owning
deploy projectsrun (26-12, TAGDEP-10). - project_
tags - Tags a project uses (quick task 261106-bt0): which
[provider]pathreferences the code of a project artifact holds, and whether a gateway’s tag export holds them. - projects
deploy/project.yamland the pure model of a project deploy (Phase 25).- pull
- The pull engine (Phase 22, DPLN-06): a live tree to a declared tree that renders back to the live effective view.
- render
- The render pipeline: a declared gateway tree to the bytes the gateway holds on disk.
- rules
- Fixed render policy: which resource types and files a declared tree may never ship, however the manifest allowlist reads (Phase 21, DRND-04).
- tag_
apply - Import batches of project-owned tags (Phase 26, 26-08, TAGDEP-05).
- tag_
canon - Canonical form of native tag JSON, for the plan diff and the verify of
project-owned tags (Phase 26, TAGDEP-08, research
## Revision 3). - tag_
converge - The backup’s copy of a run’s owned tags (Phase 26, 26-13, D-07 on pairs).
- tag_
delete - ign’s client of the
cli/tagDeleteWebDev route (26-18, D-13, TAGDEP-06). - tag_
groups - Tag groups of a project’s owned providers (Phase 26, 26-10, D-09, D-12).
- tag_
plan - The plan of a project’s owned tags against the gateway (Phase 26, TAGDEP-04, TAGDEP-11).
- tag_
record - The on-host tag record (26-06, TAGDEP-09, D-02, D-05).
- target
targets/<env>.yaml: where a rendered tree is deployed.- transport
- How a verb reads a gateway node’s resource collections (Phase 22).
- tree
- The in-memory source and rendered trees, and the render digest.
- uuid
- Deterministic
attributes.uuidfor resources that render creates (Phase 21, DRND-06, decision D-03). - verify
- Pure evaluation of
ign deploy verify(22-10, DPLN-07, DPLN-08, DPLN-09). - yamlio
- Strict YAML parsing for the declared tree (
manifest.yaml,targets/<env>.yaml).
Functions§
- component_
problem - Why
nameis not a safe single path component, orNonewhen it is.