From dfb4d0b53efb553d5d8a40b43fa3da6092feb464 Mon Sep 17 00:00:00 2001 From: LeeW Date: Wed, 26 Feb 2025 17:02:37 +0100 Subject: [PATCH] updates instructions --- README.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c03baef..f173eff 100644 --- a/README.md +++ b/README.md @@ -9,12 +9,21 @@ Roles: * New User: new key to be added; can be a new employee being added for first time, existing employee getting access to a new repo, key rotation, etc * Existing User: user who already has access to the appropriate project + * E.g. look up in the [groups](/groups/) dir + * E.g. look up in in [verify/.sops.yaml](verify/.sops.yaml) * Any User: either New User or Existing User ## 1. Onboarding: New User: create and add a gpg key -- please follow instruction on following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key -- add ONLY the _PUBLIC_ part of your gpg key!!! -- checkin via MergeRequest/PullRequest +- create a branch titled `add_pubkey_-` + - e.g. `git branch add_pubkey_test-user` + - Note: no strict naming convention for the branch, it's strictly a Human-in-the-Loop process +- please follow steps 1-13 at the following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key + - CAVEAT: step 14 is not necessary, as it is specific to a GitHub account +- add ONLY the _PUBLIC_ part of your gpg key!!! to this repo + - file format: `@netgo.de.gpg.pub` +- git: commit the new file, push +- open a MergeRequest/PullRequest +- hand-off to an Existing User for approval and further configuration ### 1b. Onboarding: Any User: Add new user to groups