local provider

[Eric Snow]

On Fri, Dec 12, 2014 at 9:26 AM, Nate Finch <nate.finch at canonical.com> wrote:
> I think one easy thing we could do to better indicate the purpose of the
> local provider is to simply rename it.  If we named it the "demo" provider,
> it would be much more clear to users that it is not expected to be used for
> deploying a production environment. This could be as easy as aliasing
> "local" to "demo" and making the default environments.yaml print out with
> the local provider renamed to "demo".  (feel free to s/demo/testing/ or any
> other "not ready for production" word)

I'd favor keeping "local" in the name, e.g. "local-only" or
"local-restricted".  A really explicit name would be even better, e.g.
"local-testing-dev-and-demos" (seriously).  Then "local" would just
alias back to it for backward compatibility.  Do we support emitting
warnings based on the environment type?  If so, we could do that for
"local".

Then to make the purpose clear we *could* register more aliases for
it. Some ideas (just brainstorming):

"demo"
"deployment-testing"
"development"
"isolated"

I'm not sure just "testing" is clear enough, particularly in relation
to the "dummy" provider.

-eric

p.s. I'd love to see local provider fixed up to work like the rest,
but I'll start another thread about that to avoid getting side-tracked
here.