Document op read vs op item get convention #143

Merged
eblume merged 1 commit from docs/op-read-convention into main 2026-02-10 13:09:56 -08:00
Owner

Summary

  • Adds guidance to CLAUDE.md: use op read for secret values, op item get only for metadata
  • Fixes the argocd login example which used op item get --fields
  • op item get --fields wraps multi-line values in quotes, which corrupts keys and other secrets

Discovered while verifying the sifaka borg repokey in 1Password — hashes didn't match until we switched to op read.

## Summary - Adds guidance to CLAUDE.md: use `op read` for secret values, `op item get` only for metadata - Fixes the argocd login example which used `op item get --fields` - `op item get --fields` wraps multi-line values in quotes, which corrupts keys and other secrets Discovered while verifying the sifaka borg repokey in 1Password — hashes didn't match until we switched to `op read`.
op item get --fields wraps multi-line values in quotes, corrupting
them. Use op read for retrieving secret values in scripts and IaC.
Also fixes the argocd login example in CLAUDE.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 0d5f48e2c2 into main 2026-02-10 13:09:56 -08:00
Sign in to join this conversation.
No reviewers
No labels
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
eblume/blumeops!143
No description provided.