Skip to content

docs: document --use-base64-encoding flag for pipectl encrypt#6754

Open
A-d-i-t-y wants to merge 1 commit intopipe-cd:masterfrom
A-d-i-t-y:docs/pipectl-encrypt-base64-flag
Open

docs: document --use-base64-encoding flag for pipectl encrypt#6754
A-d-i-t-y wants to merge 1 commit intopipe-cd:masterfrom
A-d-i-t-y:docs/pipectl-encrypt-base64-flag

Conversation

@A-d-i-t-y
Copy link
Copy Markdown

What this PR does

Adds documentation for the --use-base64-encoding flag in the pipectl encrypt command section.

Which issue this fixes

Fixes #6509

Changes

  • Added usage example with --use-base64-encoding flag
  • Added a note explaining when and why to use this flag (Kubernetes Secret data field requires base64-encoded values)

Does this PR introduce a user-facing change?

Yes — improves discoverability of an undocumented flag for users encrypting secrets for Kubernetes.

@A-d-i-t-y A-d-i-t-y requested review from a team as code owners May 9, 2026 07:47
@A-d-i-t-y A-d-i-t-y force-pushed the docs/pipectl-encrypt-base64-flag branch from 087a6f5 to 9956cb5 Compare May 9, 2026 07:58
Signed-off-by: Aditya <aaaditya1909@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document --use-base64-encoding for pipectl encrypt

1 participant