From 868de23596c21cc8606dea0bd19cba57f35338a3 Mon Sep 17 00:00:00 2001 From: Magnus Watn Date: Mon, 2 Oct 2023 14:17:08 +0200 Subject: [PATCH] Update command names in usage summary --- docs/Usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Usage.md b/docs/Usage.md index 5bfbefda..a4e8ada2 100644 --- a/docs/Usage.md +++ b/docs/Usage.md @@ -112,7 +112,7 @@ If you use git there is commit hook that prevents commiting decrypted files and - Values/Secrets data are not a part of the chart. You need to manage your values, public charts contains mostly defaults without secrets - data vs code - To use the helm-secrets plugin you should build your `.sops.yaml` rules to make everything automatic -- Use helm secrets for everyday work with you secret yaml files +- Use helm secrets for everyday work with you secret yaml files - Use version control systems like GIT to work in teams and get history of versions - Everyday search keys is simple even with encrypted files or decrypt on-the-fly with git diff config included - With example helm_vars you can manage multiple world locations with multiple projects that contain multiple environments