gitea-admin
/
communication-keys
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

ADP-216: updates README from UAT feedback for step2

Browse Source
ADP-216-uat-sops-step2_002
LeeW 10 months ago
parent 283f94e058
commit 49491471eb
1 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File

16
README.md
Unescape Escape View File

@ -42,27 +42,19 @@ Procedure:
## 1b. Onboarding: [Existing User|New User]: Add new user to groups ## 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`) 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" 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/<project_name>
ln -s ../../<path_to_key.gpg.pub>
```
Example:
### Example
Add "Max Musterman" to the group for `devnso-adp-argocd`: Add "Max Musterman" to the group for `devnso-adp-argocd`:
```shell ```shell
# navigate to group-directory for devnos # navigate to group-directory for devnso
cd groups/devnso-adp-argocd cd groups/devnso-adp-argocd
# symlink to pubkey for New User # symlink to pubkey for New User
ln -s ../../max.musterman@netgo.de.gpg.pub ln -s ../../max.musterman@netgo.de.gpg.pub

Write Preview
Loading…
Cancel
Save