From 553e1ff35c476c4f5f61d258364520505faa9e45 Mon Sep 17 00:00:00 2001 From: Kingdon Barrett Date: Tue, 27 Sep 2022 18:03:41 -0400 Subject: [PATCH] fix awkward split-phrase construction to avoid that decryption for editing with ... too many clauses in a row Signed-off-by: Kingdon Barrett --- content/en/flux/guides/helmreleases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/flux/guides/helmreleases.md b/content/en/flux/guides/helmreleases.md index a20a72ff4..c6208c1d3 100644 --- a/content/en/flux/guides/helmreleases.md +++ b/content/en/flux/guides/helmreleases.md @@ -505,8 +505,8 @@ this would work regardless but we may want to conventionally keep `values.yaml` in a file with the same name; then this rule may be a useful addition as well. The filename was also chosen to **not** match with `*.enc` or `*.encrypted` so -that `sops` CLI never infers a binary input type, to avoid that decryption for -editing with `sops my-values.enc.yaml` would also fail. +that `sops` CLI never infers a binary input type, to avoid that decryption with +`sops my-values.enc.yaml` for editing in-place would also fail. Be careful not to mix secrets with other non-sensitive data. A note that Helm stores its values as Kubernetes Secrets internally; if users can read secrets