update docs, write out long-form options

README.md

@@ -89,7 +89,7 @@ Note: For a worked-through example, see next section.
         - CLI: `${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh --list_groups`
             - Reminder: Group Name usually corresponds to Repository Name
     1.  Update sops config AND all secrets files:
-        - CLI: `${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g <group_name> $(find . -name secrets.yaml)`
+        - CLI: `${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh --group <group_name> --find_secrets
 1. **Commit the changes, Create Change Request (PR/MR)**
     1. git: commit the changes to `.sops.yaml` and secrets files (`secrets.yaml`) files
         - CLI: `git add .sops.yaml $(find . -name secrets.yaml)`
@@ -132,7 +132,7 @@ devnso-adp-argocd
 
 # For a given group, update sops config AND all secrets files - New Users cannot add themselves!
 # Output:
-% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g devnso-adp-argocd $(find . -name secrets.yaml)
+% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh --group devnso-adp-argocd --find_secrets
 # RUN: generate SOPS config
 # RUN: gpg --import *.gpg.pub
 # RUN: sops updatekeys ./loki/loki/secrets.yaml
@@ -218,7 +218,7 @@ find groups/ -name ${keyname}
 # For each group, update sops config in that repo
 # Example:
 % cd devnso-adp-argocd
-% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh -g devnso-adp-argocd $(find . -name secrets.yaml)
+% ${PATH_TO_COMMUNICATION_KEYS_REPO}/bin/update_sops.sh --group devnso-adp-argocd --find_secrets
 # now git commit, push, etc
 ```