From 2c129789ffe165f15a9397282178efae0274f892 Mon Sep 17 00:00:00 2001 From: jochens Date: Fri, 13 Nov 2026 00:19:30 +0100 Subject: [PATCH] Design 42 zfs-owns-zfs: A-26, a module declares what another resource needs before it --- .../01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md index 752ee18b..03e52c45 100644 --- a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md +++ b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md @@ -87,3 +87,8 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The - **A-25** (A-15, S2; principle 3) `${config-json}` holds no colon, so the form search that finds `${
:` does not find it: the manifest's reading also finds the exact token `${config-json}`, and a manifest that holds it needs `form:config-json`, so no node-engine that cannot write it is given the module. +- **A-26** (§1, met in develop; principles 3 and 7) §1 stands: a module declares a resource another of its resources + needs before that one, since the apply now stops at the first failure. The pacman module declares its package + before its config file, and its package fails while the config file is missing, so the stop would keep a node + from restoring its package manager: in this milestone the pacman module's config file moves before its package, + and the node-engine's probe test of that restore keeps the pacman module's own resource names, in that order.