[12:16:29] <wikibugs>	 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Re-create GitLab test instance - https://phabricator.wikimedia.org/T396622#10958322 (10Jelto) 05Open→03Resolved I'll resolve this task, the test instance is up and running again and I simplified the setup a bit and fixed...
[12:18:04] <wikibugs>	 10GitLab (Infrastructure), 06collaboration-services, 06Release-Engineering-Team: Upgrade GitLab to major version 18 - https://phabricator.wikimedia.org/T394382#10958326 (10Jelto) a:03Jelto
[15:52:56] <wikibugs>	 10GitLab (Auth & Access), 06cloud-services-team, 10Cloud-VPS, 10Toolforge: Sync WMCS GitLab group membership from LDAP - https://phabricator.wikimedia.org/T398217#10959425 (10taavi)
[17:09:34] <wikibugs>	 10GitLab (Auth & Access), 06cloud-services-team, 10Cloud-VPS, 10Toolforge: Sync WMCS GitLab group membership from LDAP - https://phabricator.wikimedia.org/T398217#10959885 (10bd808) I think this would have to be done with a bot or runbook. LDAP based group membership management is a closed extension to the...
[17:19:38] <wikibugs>	 10GitLab (Auth & Access), 06cloud-services-team, 10Cloud-VPS, 10Toolforge: Sync WMCS GitLab group membership from LDAP - https://phabricator.wikimedia.org/T398217#10959948 (10thcipriani) FWIW, there are utilities that run in systemd (managed by puppet) to manage ldap -> gitlab group sync for a few groups:...