warning: environments.yaml schema change

[Gustavo Niemeyer]

On Tue, Mar 20, 2012 at 12:35, Clint Byrum <clint at ubuntu.com> wrote:
> The agreement to drop those keys was also an agreement to ship all the
> features in 12.04's juju by February 16. That would allow beta1 users

Indeed.. it's a bit about having the cake and eating it too. There's a
serious push to have several features in juju, a serious push to have
it stable, and a serious push to have it on time. It's not a good time
for me to take sides on who's right and what might have been done
differently, but I just perceive that it's hard to have all of that at
once.

> to keep using the same configs/settings through to the release. But we
> are severly past that, and approaching beta2. Changing environments.yaml
> means digging out all the old blog posts, askubuntu questions, and basic
> documentation, and making sure we annotate them that "btw, this doesn't
> work anymore".

As an alternative, we can also have juju itself telling the user about
the change, and pointing to a URL explaining how it changed and how to
use the new mechanism.

> Can I suggest that instead of making these keys invalid, that they are
> marked as deprecated, and we simply warn users about that?

It's up to you and hazmat to decide. Just note that this is a bug.
juju *must* be able to support "deploy cs:~spamaps/precise/foobar" so
that it deploys foobar on precise. A default-image-id will break the
image selection.

-- 
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I'm not absolutely sure of anything.