previously valid amazon environment now invalid?

[roger peppe]

On 29 April 2015 at 17:10, Aaron Bentley <aaron.bentley at canonical.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2015-04-29 10:43 AM, roger peppe wrote:
>>> Once Trusty EOLs, then I think we would be able to drop
>>> functionality that 1.18 itself used only for migration.
>>>
>>> For example, if juju 1.18 had automatically created .jenvs from
>>> the environments.yaml instead of using environments.yaml
>>> directly, then when Trusty EOLed, we could drop that
>>> functionality.
>>
>> OK, this is interesting. So if we do actually want to get rid of
>> this feature, the steps would go something like:
>>
>> - implement code in current juju-core so that when the juju command
>> needs an environment and the .jenv file doesn't exist, the .jenv
>> file is created.
>>
>> - release that code as part of Ubuntu 16.04 Juju.
>>
>> - for the 21.04 release (when we no longer support 16.04 support),
>> we can remove the fallback feature.
>>
>> Is that about right?
>
> Yes, I think so.

So, to go back to the orgin of this thread:
Nate, only 6 short years until your issue can be fixed!

> There's no wiggle room.  As William said, "if you're removing or
> changing an API, or removing or changing the meaning of a command line
> flag, you are Doing It Wrong."

FWIW I seem to remember some command line flags being deprecated
(with a visible warning message) and then removed. I wonder if that might
be another possible approach that could let us avoid unbounded
code cruft accumulation.

 cheers,
    rog.