Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
A-d-i-t-y wants to merge 1 commit into
base: master
Choose a base branch
from
+12 −0
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/content/en/docs-dev/user-guide/command-line-tool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -354,6 +354,18 @@ You can encrypt it the same way you do [from the web](../managing-application/se
--piped-id={PIPED_ID} \
--input-file={PATH_TO_SECRET_FILE}
```
- With Base64 encoding (for Kubernetes Secrets):

pipectl encrypt \
--address={CONTROL_PLANE_API_ADDRESS} \
--api-key={API_KEY} \
--piped-id={PIPED_ID} \
--use-base64-encoding \
--input-file={PATH_TO_SECRET_FILE}

Note: Use `--use-base64-encoding` when encrypting secrets for Kubernetes.
Kubernetes Secret `data` field requires values to be base64-encoded.
This flag base64-encodes the value before encrypting it.

Note: The docs for pipectl available command is maybe outdated, we suggest users use the `help` command for the updated usage while using pipectl.

Expand Down
Loading