diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-10 00:18:05 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-10 00:18:05 -0500 |
| commit | 358e350299346e88fd57f923ef27ec79b7bd8728 (patch) | |
| tree | 93386879689a46e575164162cd8112a60ae63d73 /scripts | |
| parent | 859ba3dd61cdb5b0ebd9a1849b5c6fc6ffb41fdd (diff) | |
| download | rulesets-358e350299346e88fd57f923ef27ec79b7bd8728.tar.gz rulesets-358e350299346e88fd57f923ef27ec79b7bd8728.zip | |
docs(spec-review): check generated config resolves where consumed
A generated config gets read in a different namespace than the one that wrote it. Build host, chroot, image runtime, target system, container, and VM are distinct, so a path valid where the config is generated can be absent where it's read. I added the check to the Architecture & maintainability dimension.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions