Comment 3 for bug 1205466

Agreed -- removing all units and destroying service would behave
differently, that makes sense.

On Fri, Jul 26, 2013 at 1:58 PM, Mark Ramm <
<email address hidden>> wrote:

> After a bit of discussion, we came to the idea that if we just treat the
> cache as completely service-name based, and destroy-service destroys
> everything -- including that service name's cached charms -- the whole
> thing seems reasonable and unsurprising in all the cases we care about.
>
> IMHO, if the unit count goes down to zero that would not have the same
> result. Only destroy-service would clear out the cache and along with
> all other info about the old service configuration.
>
> ** Changed in: juju-core
> Importance: Undecided => Medium
>
> ** Changed in: juju-core
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1205466
>
> Title:
> deploy charm uses cached copy even when all services are removed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1205466/+subscriptions
>

--
David Britton <email address hidden>