<div dir="ltr">Oh I see.  Yes, I agree that we should always try the right way first and only use the provider if necessary (especially if using the provider leaves garbage around).  <div><br></div><div>It seems like there's no reason why we couldn't make a --force flag do it that way in 2.0 (aside from time constraints).</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 6, 2016 at 10:48 AM Aaron Bentley <<a href="mailto:aaron.bentley@canonical.com">aaron.bentley@canonical.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
On 2016-04-06 10:45 AM, Nate Finch wrote:<br>
> Wait, didn't destroy-environment --force fall back to the provider?<br>
> I thought that was the whole point of --force<br>
<br>
No, it didn't fall back.  It uses the provider unconditionally,<br>
without trying a normal destroy-controller first.<br>
<br>
Aaron<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
iQEcBAEBCAAGBQJXBSG5AAoJEK84cMOcf+9hzSQIAJ/vNKIa1/TnDSyvC2U9ApzW<br>
TAEvSqaEUw0ZL2dl2tiNKTp3JPzcnCR4VKrBIsh1xi0hB1UNtJR+IW4O46gRI6ok<br>
ZvA1cAvoJvRdmqf1ntNzYwHRSn/Tm82DGzixTPt0TcTn3KYrk13XpRJuxMbbvHDM<br>
LfYG0zglGmVKUaWs4rBogh4H4OaiOIR8lORXSC8GRQjA1/C4c+FjIg+KeW5Yw2Ti<br>
XnG87BPyJ1TtPGWxxeKAk4tnkZwnZKtJOnHU/IfvTFOpECdBjojWnnc6VbQ1um0H<br>
WwjR6EcA4qxkkhND6ypIGkt9A4k3ZZvckCau52EgIn3pnwhk5OSw64MURJAEmn0=<br>
=vm/H<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div>