Wait, didn't destroy-environment --force fall back to the provider? I thought that was the whole point of --force
On Wed, Apr 6, 2016 at 10:24 AM Aaron Bentley <aaron.bent...@canonical.com> wrote: > On 2016-04-06 08:22 AM, Andrew Wilkins wrote: > > What I would like to see is: * destroy-controller to take on a > > --force flag, causing it to do what kill-controller does now, and > > what destroy-environment --force used to do > > What kill-controller does now, where it attempts to use Juju, but > falls back to the provider, is much more valuable to us in QA than > what destroy-environment --force used to do. We don't want to leak > resources unnecessarily, but we do want things to die when we try to > kill them. >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
