- please follow instruction on following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
- please follow instruction on following link: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
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"
```bash
cd roles/<project_name>
ln -s ../../<path_to_key.gpg.pub>
```
## 2. Offboarding: Archive Expired Keys (EOL)
To mark a key as expired, move it to the `archive/` dir as follows:
To mark a key as expired, move it to the `archive/` dir as follows:
@ -24,6 +34,30 @@ To mark a key as expired, move it to the `archive/` dir as follows:
Context: This repo stores the keys used to encrypt secrets in other repos; these "consumer" repos each contain a sops config `.sops.yaml` which manages access to the encrypted files (e.g. `secrets.yaml`)
The following commands explain how to update the `.sops.yaml` for a repository: