s/roles/groups/g , iteration

README.md

@@ -17,12 +17,12 @@ gpg --import /path/to/keys/*.gpg.pub
 gpg --list-keys --keyid-format=long
 
 
-### roles
+### groups
 
-Access for each repo is tracked using the `./roles/` directory; each sub-directory represents a "role" or "group". (Naming: choosing "role" as the name and deciding to just have "one group per role"
+Access for each repo is tracked using the `./groups/` directory; each sub-directory represents a "group" (Note: some "groups" are also "roles", e.g. `admin`)
 
 ```bash
-cd roles/<project_name>
+cd groups/<project_name>
 ln -s ../../<path_to_key.gpg.pub>
 ```
 
@@ -46,14 +46,14 @@ The following commands explain how to update the `.sops.yaml` for a repository:
 % git clone git@git.dev-at.de:cloud-solutions/nso/devnso-adp-argocd.git
 % cd devnso-adp-argocd/
 
-# List available roles
-% ${PATH_TO_THIS_REPO}/bin/update_sops.sh --list_roles
-# INFO: listing roles
+# List available groups
+% ${PATH_TO_THIS_REPO}/bin/update_sops.sh --list_groups
+# INFO: listing groups
 admin
 automation
 devnso-adp-argocd
 
-# For a given role, update sops config and specified secrets file
+# For a given group, update sops config and specified secrets file
 % ${PATH_TO_THIS_REPO}/bin/update_sops.sh -r devnso-adp-argocd -s ./adp-api-devs/adp-api-devs/secrets.yaml
 % git diff
 ```