1.7 KiB
PR#102: config/werkprobe.toml holds the host config of werkprobe
WARNING: This document describes only the change applied in this PR. It may already be outdated once the next PR is merged. Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.
Related Links
- werkrevisor PR#101:
tools/sync-host-configfound the drift.
Problem
The machine config of werkprobe on mih09 differs from config/werkprobe.toml in five keys:
there, Jev judges every changed file, the model only advises, the hard paths hold only secrets,
and the build and CI paths are judged paths.
The human decided that the host is right.
Most tests take config/werkprobe.toml as their base, so the change of the file would change them.
Non-Goals
- No change of the review of werkprobe: the host keeps its values.
- No change of what a test checks.
Solution
config/werkprobe.toml gets the five values of the host:
[engine] model_role = "advises", [hard_yellow] paths with the secret paths only,
[hard_yellow] judged_paths with the build and CI paths, and [path_judge] judge = "jev" and scope = "all".
tools/sync-host-config then finds no differing key, only comments; --apply after the merge makes the block equal.
The tests get their own base, tests/fixtures/test-config.toml: config/werkprobe.toml as it was before this PR.
tests/fakes.py names it TEST_CONFIG; every test that read config/werkprobe.toml as a base reads it now.
The tests of the example configs keep reading config/.
Additional Changes
- The operations document names the hard paths and the path judge of werkprobe, and version 0.41.1.
Open Questions
None.
Follow-up PRs
None.