previously valid amazon environment now invalid?

[roger peppe]

On 28 April 2015 at 19:41, Nate Finch <nate.finch at canonical.com> wrote:
> No one seems to be answering my actual question. That error message seems
> new. Is it?  Either way, the error message is incorrect - control bucket is
> not required - and whatever is emitting that message needs to be fixed.

The error message isn't new - it's been like this since 1.18.

>From the point of view of the "fall back to environments.yaml if we
don't find a .jenv file" code, the control-bucket *is* required.
That's why I think the real solution here is to eliminate that
fallback code, the source of your confusion.

  cheers,
    rog.