pi-provider add refuses a fork whose secrets/pi-credentials directory does not exist yet #80
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/nexus#80
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On a deployment forked from the public template, the first
pi-provider addstops withplanned 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 missingsecrets/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 nomkdirby 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.