Comment 8 for bug 1680683

On 12 April 2017 at 13:32, John A Meinel <email address hidden> wrote:

> One major caveat is that if these are "local" charms, we really don't know
> if you have a copy if you ever had to go back to a version that isn't your
> current version. So I don't think we could prune automatically. That said,
> we could provide commands to manage/cleanup your cached charm revisions
> manually.

I would not call this a major caveat. I don't think anyone has ever
wanted to revert a charm this way, and it is always done by retrieving
a known good version and reuploading to the controller. Reverting to
'local-14' is never done because there is no way of knowing what
'local-14' actually is without reverting to it, and at that point it
is too late and your system potentially destroyed.

I would recommend cleanup happening automatically, perhaps with tuning
('last N revisions'), rather than requiring people to manually cron
this for each controller or model and deal with the support requests
from people who didn't follow best practice and allowed their mongodb
to grow unbounded.

--
Stuart Bishop <email address hidden>