pi-provider add refuses a fork whose secrets/pi-credentials directory does not exist yet #80

Open
opened 2026-10-06 03:50:04 +01:00 by vnprc-agent · 0 comments

On a deployment forked from the public template, the first pi-provider add stops with planned parent directory is unavailable: <secrets>/secrets/pi-credentials. The template ships no Pi credential, git cannot track an empty directory, so the parent of the credential's token directory does not exist until something creates it, and the tool refuses rather than creating it.

Creating secrets/pi-credentials/<credential>/ is already a recorded step of the transaction. Proposal: creating the missing secrets/pi-credentials/ parent is recorded the same way, so rollback and recovery remove it when the run that created it is undone, and a fresh fork's first credential needs no mkdir by hand. The alternative, a placeholder file in the template, puts a file in every fork for the sake of one command's precondition.

Found on the public install walk, declaring the first provider on a forge-less deployment.

On a deployment forked from the public template, the first `pi-provider add` stops with `planned parent directory is unavailable: <secrets>/secrets/pi-credentials`. The template ships no Pi credential, git cannot track an empty directory, so the parent of the credential's token directory does not exist until something creates it, and the tool refuses rather than creating it. Creating `secrets/pi-credentials/<credential>/` is already a recorded step of the transaction. Proposal: creating the missing `secrets/pi-credentials/` parent is recorded the same way, so rollback and recovery remove it when the run that created it is undone, and a fresh fork's first credential needs no `mkdir` by hand. The alternative, a placeholder file in the template, puts a file in every fork for the sake of one command's precondition. Found on the public install walk, declaring the first provider on a forge-less deployment.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
allod/nexus#80
No description provided.