pi-provider: print the exact commit and re-lock lines, and the check that they took #82

New issue

Open

opened 2026-10-06 05:25:40 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-10-06 05:25:40 +01:00

After a live add, pi-provider prints "Review and commit the profiles/secrets changes" and "Update the private deploy pins". On the first run on a fresh fork the operator committed the secrets clone and not the profiles clone, then re-locked the deploy flake, which refused to write the lock because a git+file input was dirty and still exited 0, then rebuilt a VM that had no provider. Three steps looked done and none were.

Proposal: the follow-up block names the files it wrote in each clone as the exact commit lines (git -C <profiles> commit -m '...' pi-providers.json, git -C <secrets> commit -m '...' pi-credentials.json secrets/pi-credentials/<credential>/), the re-lock line with --refresh and the jq line that reads both pinned revisions back, and says to stop when a revision did not move. The tool still performs none of it; it stops guessing that the operator knows the sequence.

Found on the public install walk.

After a live `add`, `pi-provider` prints "Review and commit the profiles/secrets changes" and "Update the private deploy pins". On the first run on a fresh fork the operator committed the secrets clone and not the profiles clone, then re-locked the deploy flake, which refused to write the lock because a `git+file` input was dirty and still exited 0, then rebuilt a VM that had no provider. Three steps looked done and none were. Proposal: the follow-up block names the files it wrote in each clone as the exact commit lines (`git -C <profiles> commit -m '...' pi-providers.json`, `git -C <secrets> commit -m '...' pi-credentials.json secrets/pi-credentials/<credential>/`), the re-lock line with `--refresh` and the `jq` line that reads both pinned revisions back, and says to stop when a revision did not move. The tool still performs none of it; it stops guessing that the operator knows the sequence. Found on the public install walk.

vnprc-agent referenced this issue from allod/archetypes

2026-10-06 05:28:32 +01:00

Forge-less dev VM: first managed Pi provider does not reach the VM after rebuild #134