From 49491471eb0edcdc18a76d225d573e471a8e6810 Mon Sep 17 00:00:00 2001 From: LeeW Date: Thu, 6 Mar 2025 16:10:41 +0100 Subject: [PATCH] ADP-216: updates README from UAT feedback for step2 --- README.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index bcd0a0f..b885a4c 100644 --- a/README.md +++ b/README.md @@ -42,27 +42,19 @@ Procedure: ## 1b. Onboarding: [Existing User|New User]: Add new user to groups -Determine the groups to which access is needed, e.g. a specific repository. +**Prerequisite**: Determine the groups to which access is needed, e.g. a specific repository. If uncertain, ask a Team Member for help! -If uncertain, ask a Team Member for help! - -Technical Instructions - please forgive the complexity +**Technical Instructions** - please forgive the complexity 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`) Most of the groups correspond directly to git repository names, aka "project name" -Create a symlink from the group-directory back to the keyfile -```shell -cd groups/ -ln -s ../../ -``` - -Example: +### Example Add "Max Musterman" to the group for `devnso-adp-argocd`: ```shell -# navigate to group-directory for devnos +# navigate to group-directory for devnso cd groups/devnso-adp-argocd # symlink to pubkey for New User ln -s ../../max.musterman@netgo.de.gpg.pub