From f30d7472ddf8b6bae4bbdeaf8bec5eee4a92c765 Mon Sep 17 00:00:00 2001 From: LeeW Date: Wed, 5 Mar 2025 14:04:02 +0100 Subject: [PATCH] clarifies README --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8497db1..b321720 100644 --- a/README.md +++ b/README.md @@ -81,19 +81,19 @@ The following commands explain how to update the `.sops.yaml` for a repository: ```shell # List available groups -% ${PATH_TO_THIS_REPO}/bin/update_sops.sh --list_groups +% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh --list_groups # INFO: listing groups admin automation devnso-adp-argocd # For a given group, update sops config -% ${PATH_TO_THIS_REPO}/bin/update_sops.sh -g devnso-adp-argocd +% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g devnso-adp-argocd # RUN: generate SOPS config # WARN: no secrets file passed in, make sure to call 'sops updatekeys' on secrets files # [OPTIONAL] For a given group, update sops config AND specified secrets file -% ${PATH_TO_THIS_REPO}/bin/update_sops.sh -g devnso-adp-argocd -s ./adp-api-devs/adp-api-devs/secrets.yaml +% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g devnso-adp-argocd -s ./adp-api-devs/adp-api-devs/secrets.yaml # commit the changes to any .sops.yaml or secrets files, e.g. with ## OPINIONATED GIT - use preferred method @@ -154,7 +154,7 @@ find groups/ -name ${keyname} # For each group, update sops config in that repo # Example: % cd devnso-adp-argocd -% ${PATH_TO_THIS_REPO}/bin/update_sops.sh -g devnso-adp-argocd +% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g devnso-adp-argocd # now git commit, push, etc ```