From https://secure.phabricator.com/T11856#200111
Certificates have been deprecated in favor of tokens
See also T123514: [Phragile] Use Conduit API-Tokens instead of certificates
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T163581 User's Bugzilla era comments not (yet) merged into their Phabricator account | |||
| Declined | None | T242860 bzimport uses deprecated certificate auth |
Event Timeline
Comment Actions
Proposing to decline this task and to archive the account @bzimport as I don't think it will ever be used again
Comment Actions
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
Comment Actions
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'm refering to https://www.mediawiki.org/wiki/Phabricator/Help/Reclaim_Bugzilla_and_RT_accounts
Comment Actions
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?
Comment Actions
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.
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2020-01-15T22:40:14Z] <mutante> phabricator - disabling 'bzimport' user (T242860)
Comment Actions
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.
Comment Actions
priority normal now that the user is disabled ? (disabled != deleted, so it could be re-enabled)
Comment Actions
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?
Comment Actions
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?
Not sure anyone on this ticket will be able to answer, anyway:
https://wikitech.wikimedia.org/wiki/RT states that procurement@ is still being handled in RT. Is that correct or is that outdated?
(Cannot check myself as I cannot get into RT anymore, https://idp.wikimedia.org/login nowadays tells me "Service access denied due to missing privileges.")
Given that the S4 space and procurement exist, are there any RT tickets from >6y ago that SRE really wants to still import into Phab? Are there stats / do we know if people still access rt.wikimedia.org to check historical tickets, so RT has not been sunsetted yet (cannot find a ticket about sunsetting)?
Comment Actions
@bzimport account has been disabled, after more than 5 years of the Bugzilla to Phabricator migration, and the migration code is not maintained anymore. Declining to reflect reality.