People keep writing them, in defiance of sane layering and explicit instructions, for the most embarrassingly trivial tasks (statushistorypruner? dblogpruner? txnpruner? *all* of those can and should pass through a simple api facade, not just dance off to play with the direct-db-access fairies.)
There is no justification for *any* of those things to see a *state.State, and I'm going to start treating new workers that violate layering this way as deliberate sabotage attempts. Leads who have overseen the introduction of those workers, sort it out.
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
