Document op read vs op item get convention (#143)
## 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`. Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/143
This commit is contained in:
parent
d045a5d76a
commit
0d5f48e2c2
2 changed files with 4 additions and 1 deletions
1
docs/changelog.d/docs-op-read-convention.doc.md
Normal file
1
docs/changelog.d/docs-op-read-convention.doc.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
Document `op read` vs `op item get` convention for 1Password secret retrieval
|
||||
Loading…
Add table
Add a link
Reference in a new issue