When adding users to unix group we try to have an engineering manager responsible for the general area of operations approve the access request. This is something that has happened in a somewhat add hoc way in the past however it would be useful going forward to assign engineering managers to all groups in the admin data.yaml file. This makes it easier for SRE engineers who are managing the clinic duty fine the correct list of approvers.
With this in mind i have generated a list of all the group which currently have no approvers and the roles that theses group give access to. I have tried to go through the list manually and assign managers which seem appropriate to me, however i have likely got some of theses wrong so please let me know where i have need to make corrections. Further there are still a bunch of group which are left blank so if people could either claim theses groups or suggest owners that would be very much appreciated.
Task description has been updated to list the remaining groups without a approval contact (except groups marked as deprecated):
- airflow-search-admins
- analytics-research-admins (removed)
- analytics-search-users
- analytics-wmde-users
- cassandra-test-roots
- contint-docker
- dataset-admins
- deploy-aqs
- deploy-design
- deploy-service
- deployment-docker
- deployment-jenkins
- dns-admins
- druid-admins
- htmldumps-admin
- ldap-admins
- logstash-roots
- mailman3-roots
- maintenance-log-readers
- mediawiki-testers
- mw-log-readers
- pentesters
- perf-roots
- perf-team
- releasers-blubber
- releasers-mediawiki
- releasers-mobile
- releasers-mwcli
- releasers-wikidiff2
- restbase-admins
- restbase-roots
- sessionstore-roots
- traceback-roots (removed)
- udp2log-users
- varnish-log-readers
- wmcs-admin