previously valid amazon environment now invalid?

[roger peppe]

The .jenv code was introduced prior to 1.16. How far back
in time do we need to preserve compatibility? (genuine
question)

If transitioning to the new scheme is really an issue, it
would be easy to write a very simple tool that would
allow a .jenv file to be created from an existing environments.yaml
entry.

Or is the issue perhaps not just one of backward compatibility, but
that people are actually relying on this (ostensibly only-for-compatibility)
functionality even for environments bootstrapped since 1.16?

  cheers,
    rog.

On 28 April 2015 at 15:36, Aaron Bentley <aaron.bentley at canonical.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2015-04-27 05:30 PM, roger peppe wrote:
>> That fallback code was designed to be around for only a short time
>> - I'd suggest removing it.
>
> We have bugs about the fact that the fallback code has been removed:
>
> https://bugs.launchpad.net/juju-core/+bug/1437191
>
> Juju is supposed to be compatible back to 1.18.  Please do not remove
> compatibility code in the future.

The .jenv storage was introduced prior to 1.18. Does juju-core need
to preserve compatibility
>
> Aaron
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJVP5sBAAoJEK84cMOcf+9hPSgIAKUn90cMRb3rAvKRhIgXNlLp
> I9mOtqLWBo2APwW0RqXPM9XJyK4nn7Im394ORXLdYZv2/0BfJtHNys8M8Tq7gk9B
> LBN3NdrI0g/LJQsuUa/6ciZ+P07fG8Xd7OMakr2evUDFPuneZ8foAi8rK7NCWkO5
> TXYBh8FmRl8n0m5u9yAkEAHC9i16Dm20/hTuWPJBknqv2u/r6Y2JymnKuPCJa7ye
> /CQcTAuK1xpFk40fMYwGZ1AJLT6ZP0xTEpGAp3BPZrSZra9sAfwRcCPblXvKo8pG
> JzfGHTgVHCvXq/7SoJJ3glWpWMg+dcAG08mAN47Y8PNpI7R8IGyBpW0Pz4jJIOs=
> =YmBa
> -----END PGP SIGNATURE-----
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev