Page MenuHomePhabricator

Pull data from Conduit instead of custom database dump
Closed, DeclinedPublic

Description

History:
Phlogiston pulls data from a custom, daily dump of Phabricator data. It was built this way, instead of using Conduit, for [historical reasons I don't remember - maybe Conduit wasn't considered stable enough in 2015, or maybe it lacked some key feature?]. We could rewrite Phlogiston to use Conduit instead.

Pro:
Would update data in real-time instead of daily. Possibly better support since Phlogiston is the only customer of its dump (afaik) while Conduit is more shared.

Con:
Would require a complete rewrite of the loading portion of Phlogiston. Could introduce security issues, since Phlogiston dump has been screened and tested in production against security data leaks.

Event Timeline

Historical note: I believe at the time Phlogiston was designed, conduit did not expose transaction data for moving a task between columns within a project. I don't know if conduit supports this now.

There may have been other limitations as well.

Historical note: I believe at the time Phlogiston was designed, conduit did not expose transaction data for moving a task between columns within a project.

This. ^^

I don't know if conduit supports this now.

Maybe™: T123417#3604696

In T175872, @JAufrecht wrote:

Could introduce security issues

I trust a proper maintained upstream API more when it comes to access control implementation than some downstream low-level DB dump with hacks on top of it.

Phlogiston is unmaintained. Declining its remaining open tasks. See T253964 for more info.