Document --use-base64-encoding for pipectl encrypt
Open
@antedotee is already working on this.
Since Feb 7, 2026.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
The docs for pipectl encrypt in docs-dev only mention stdin and --input-file, but the CLI supports --use-base64-encoding. Users won’t discover this option from the docs, even though it changes input handling semantics and may be required for certain payloads.
What you expected to happen:
Docs should list --use-base64-encoding as an optional flag for pipectl encrypt, with a short explanation of when to use it.
Evidence:
pipectl encrypt --help shows:
--use-base64-encoding Whether the plaintext should be base64 encoded before encrypting or not. (default false)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.