mirror of
https://gitlab.archlinux.org/archlinux/infrastructure.git
synced 2024-09-28 20:51:20 +02:00
264eff7dac
Strictly speaking this is not a devops duty, but I believe this is currently the best place to ensure we won't ever forget to create a keyring revocation ticket for an offboarded former staff.
1.9 KiB
1.9 KiB
Offboarding an Arch Linux team member
Details
- Team member username:
- Currently held roles:
- Removal request:
- Voting result:
All roles checklist
- Remove user email by reverting instructions from
docs/email.md
. - Set user to inactive in archweb: https://www.archlinux.org/admin/auth/user/
TU/Developer offboarding checklist
- Remove entry in
group_vars/all/archusers.yml
. - Remove SSH pubkey from
pubkeys/<username>.pub
. - Run
ansible-playbook -t archusers playbooks/*.yml
. - Remove the user from the
Trusted Users
/Developers
groups on Keycloak. - Moderate email address on arch-dev-public (find member and moderate)
- Remove member from arch-tu mailing lists
- Remove member from staff mailing lists
- Create keyring revocation ticket
DevOps offboarding checklist
- Remove entries in
group_vars/all/root_access.yml
. - Run
ansible-playbook -t root_ssh playbooks/*.yml
. - Run
ansible-playbook playbooks/hetzner_storagebox.yml playbooks/rsync.net.yml
. - Remove the user from the
DevOps
group on Keycloak. - Remove member from arch-devops-private mailing lists
- Remove pubkey from Hetzner's key management
Wiki Administrator checklist
- Remove the user from the
Wiki Admins
group on Keycloak. - Remove member from arch-wiki-admins mailing list.