Striker needs a Phabricator bot account with membership in the Repository-Admins group. This account will be used by Striker to create new diffusion repositories.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • yuvipanda | T111885 Initial Deployment of Kubernetes to Tool Labs | |||
| Open | None | T117071 Figure out a git hosting solution for tools/kubernetes | |||
| Resolved | bd808 | T102066 Make sure tools can be taken over after they are abandoned | |||
| Resolved | bd808 | T102081 Provide an easy way for Tool Labs tools to expose their source code | |||
| Open | None | T128158 Tools web interface for tool authors (Brainstorming ticket) | |||
| Resolved | bd808 | T133252 Create application "Striker" to manage Diffusion repositories for a Tool Labs project | |||
| Resolved | bd808 | T136256 Deploy "Striker" Tool Labs console to WMF production | |||
| Resolved | mmodell | T142539 Create Phabricator bot account for Striker |
Event Timeline
Comment Actions
@bd808: I'm not sure I have a preference but it sounds like maybe a better idea to create the account through wikitech since I don't think we can attach a bot account to ldap after-the-fact.
Comment Actions
@mmodell I went ahead and made the @StrikerBot account via a wikitech LDAP association. Can you use your database super powers to set the "bot" flag on it like you did for @Stashbot?