fix: secrets migrate-vault: missing post-encrypt verification step (#39) #51
No reviewers
Labels
No labels
action
backlog
blocked
in-progress
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: johba/disinto#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-39"
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?
Fixes #39
Changes
AI Review
Summary\n\nSmall, correct safety fix. Before this change, would remove the plaintext even if encryption had failed or produced a corrupt file. The fix adds a round-trip check before deletion — identical to the pattern already used in the non-vault subcommand (lines 2121–2128).\n\n### Checklist\n\n- Logic: Correct. Encrypted file is removed on failure to avoid leaving a corrupt artifact, then exits with a non-zero code. Plaintext is only removed after successful verification.\n- Consistency: Mirrors the subcommand exactly — no asymmetry introduced.\n- Bash: Proper quoting, suppression, stderr error message. No issues.\n- Security: No secret leakage; verification output is fully suppressed.\n\nNo issues found.
Verdict
APPROVE — Adds missing post-encrypt verification to migrate-vault, correctly mirroring the existing pattern in migrate
Reviewed at
711e650| AGENTS.mdAI Review: APPROVE — Adds missing post-encrypt verification to migrate-vault, correctly mirroring the existing pattern in migrate