Sure, that's a valid outcome :).
Though in that case, we should also clean it up out of puppet, cleaning up phabtools and phabtools_user etc from puppet - https://github.com/wikimedia/puppet/search?q=phabtools&unscoped_q=phabtools if it's no longer needed
Might need a bit of unravelling etc
Is @bzimport the account used to import previous activity from bugzilla to Phabricator? If so, do you think we should inform people before shutting down the import service to give folks the last chance to import their BZ activity into Phab (so tickets are properly attributed, etc.?)
I cannot imagine that the import script still works, given code changes and DB schema changes over the last 5+ years since we moved from Bugzilla to Phabricator.
Plus I don't think that has anything to do with accessing the account @bzimport?
https://phabricator.wikimedia.org/people/manage/829/ there i a "Disable user" link on "manage" page for it. Should we click? @20after4 agrees?
edit: bot user has been disabled. disabled is not the same as deleted.
regarding cleanup, not sure if we really want to delete the entire phabtools auth.
it was added in https://gerrit.wikimedia.org/r/c/operations/puppet/+/192856
phabtools.conf is a config file used by the migration logic, and ongoing history assignment logic that was unpuppetized for reasons that are now fixed.
There are some RT tickets that have not been imported and RT is still alive. There is a small chance we might want to use that to import them as private tickets instead of needing to create an RT-static to keep them and get rid of RT. Maybe let's first just remove the Bugzilla part but not both?