Canonical Juju

LastLogTracker accesses mongo collections directly

Bug #1602508 reported by Ian Booth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Low
Unassigned

Bug Description

The LastLogTracker in state/logs.go accesses mongo collections directly instead of using Juju's collection abstractions. All access to mongo should be via Juju's abstractions.

Tags: tech-debt 2.0
Anastasia (anastasia-macmood)
Changed in juju-core:
milestone: 2.0-rc1 → 2.0.0
Richard Harding (rharding)
Changed in juju-core:
milestone: 2.0.0 → 2.1.0
Canonical Juju QA Bot (juju-qa-bot)
affects: juju-core → juju
Changed in juju:
milestone: 2.1.0 → none
milestone: none → 2.1.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

As this is a tech-debt item, I am lowering its priority and removing from the milestone.

tags: added: tech-debt
Changed in juju:
importance: High → Low
milestone: 2.1.0 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

There has been a lot of re-work in the area. In fact, I can no longer find "LastLogTracker" anywhere in our codebase. I believe that this report is no longer valid.

Changed in juju:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.