This ideally will preserve all other state for the tool itself and is easily seen and surfaced by every on working in the Tool Labs environment.
Outcomes:
block logins of the tool (and flag attempts to syslog) stop all running jobs and webservices
Questions:
disable all cronjobs? block outgoing/ingoing mail? block database credentials (revoke replica creds)?
What should and shouldn't this do?
Clear yes:
Maybe:
Probably not?:
Current best blocking technique is is blocking the user's Developer account on Wikitech. This will disable ssh access to all Cloud VPS instances. It will not launch any intelligent agent to kill processes (including ssh sessions) that are already active.
@Andrew Does your script solve that issue? (or a slightly modified version of it)
Maybe we just need to document it :)
The topic of this doesn't quite fit with the initial description. I /think/ that T170355 is the same ask (and it's done, and somewhat documented) but I'm confused by the 'for a user' in the task title.
I think this is more focused on quickly blocking a user that's suspected of bad behavior, but not really deleting the tool, just blocking access. Note that this task predates me by many years, so I'm just guessing on the use-case that triggered the creation of the task.