Comment 2 for bug 896378

I like this so +1 from me.

I'm not 100% sure of how this should be implemented but, I agree with the
sentiment of being able to operate on diff. environments while at the same
time not having to explicitly name them on every command.

Thanks,

Juan

On Fri, Nov 25, 2011 at 11:00 AM, Jorge O. Castro <email address hidden> wrote:

> Public bug reported:
>
> I like that I can "juju bootstrap -e my-ec2-environment"
>
> But then I need to add a "-e my-ec2-environment" from then on when I am
> deploying and adding stuff. That's alot of typing! How about like how
> VCS systems do it:
>
> $ juju bootstrap -e my-ec2-environment
> Environment now set as my-ec2-environment
> type: ec2
>
> (then do stuff, no need to be explicit with the -e, then when I want to
> use my local stuff:)
>
> $ juju switch-environment my-local-thing
> Environment now set as my-local-thing
> type: local
>
> Then do stuff, I can then switch to any of my environments by demand,
> and then we just have convenience commands for it like:
>
> juju list-environments - shows every one I've configured
> juju environment - shows me which environment I am currently in.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> https://bugs.launchpad.net/bugs/896378
>
> Title:
> -e should remember the environment in that session
>
> Status in juju:
> New
>
> Bug description:
> I like that I can "juju bootstrap -e my-ec2-environment"
>
> But then I need to add a "-e my-ec2-environment" from then on when I
> am deploying and adding stuff. That's alot of typing! How about like
> how VCS systems do it:
>
> $ juju bootstrap -e my-ec2-environment
> Environment now set as my-ec2-environment
> type: ec2
>
> (then do stuff, no need to be explicit with the -e, then when I want
> to use my local stuff:)
>
> $ juju switch-environment my-local-thing
> Environment now set as my-local-thing
> type: local
>
> Then do stuff, I can then switch to any of my environments by demand,
> and then we just have convenience commands for it like:
>
> juju list-environments - shows every one I've configured
> juju environment - shows me which environment I am currently in.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/896378/+subscriptions
>
>