Make setup-tracked-hooks registry path configurable #108

New issue

Open

opened 2026-07-18 17:25:32 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-07-18 17:25:32 +01:00

Contributor

Problem

git-hooks/setup-tracked-hooks looks for the repository registry at a fixed checkout path, ~/work/allod/inventory/scripts/repositories.json. That works for the public template layout, but deploy forks may intentionally clone the inventory repo under a different alias or checkout path. In that layout the hook setup prints registry not found and exits 0, so tracked hook installation silently stops.

Desired shape

Resolve the registry path from configuration available when the dev VM home activation runs, rather than from one hard-coded checkout path. The framework already knows each composed machine's inventory checkout layout at build time, so a packaged script argument or generated wrapper is preferable to relying on an operator-session environment variable.

Acceptance

The public template behavior stays unchanged.
A deploy fork can point inventory at a non-~/work/allod/inventory checkout and still install tracked hooks during dev VM home activation.
Missing registry remains non-fatal if that is intentional, but the configured path is the one checked.

## Problem `git-hooks/setup-tracked-hooks` looks for the repository registry at a fixed checkout path, `~/work/allod/inventory/scripts/repositories.json`. That works for the public template layout, but deploy forks may intentionally clone the inventory repo under a different alias or checkout path. In that layout the hook setup prints `registry not found` and exits 0, so tracked hook installation silently stops. ## Desired shape Resolve the registry path from configuration available when the dev VM home activation runs, rather than from one hard-coded checkout path. The framework already knows each composed machine's inventory checkout layout at build time, so a packaged script argument or generated wrapper is preferable to relying on an operator-session environment variable. ## Acceptance - The public template behavior stays unchanged. - A deploy fork can point inventory at a non-`~/work/allod/inventory` checkout and still install tracked hooks during dev VM home activation. - Missing registry remains non-fatal if that is intentional, but the configured path is the one checked.