Why dont we keep the same config and just have multiple servers defined in single config file.
The shell prompt can then display the env name you are working on. Example of prompt: Cloudmonkey [ACS41QA] # Thanks Ilya -------- Original message -------- From: Sebastien Goasguen <run...@gmail.com> Date: To: cloudstack-dev@incubator.apache.org Cc: aemne...@gmail.com Subject: Re: [DISCUSS] CloudMonkey profiles to manage multiple CS instances On Mar 18, 2013, at 4:19 PM, Rohit Yadav <bhais...@apache.org> wrote: > On Tue, Mar 19, 2013 at 1:44 AM, Ahmad Emneina <aemne...@gmail.com> wrote: >> +1 I was actually wishing for this, this morning! > > Alright will push the change tomorrow, the fix is simple, we'll also > change fixed/hard-coded caching file path and add option for people to > configure colors (themes for cloudmonkey colored output). > Could you provide default paths ( I like the way it is right now :) ) I don't want to provide paths of config file as param every time... > Cheers. > >> >> >> On Mon, Mar 18, 2013 at 12:20 PM, Musayev, Ilya <imusa...@webmd.net> wrote: >> >>> Would like to get the feel of what community thinks of having "profile" >>> abilities in CloudMonkey. >>> >>> I have multiple CS instances at the moment and AFAIK I have to reconfigure >>> CloudMonkey for each when I have to switch - when working on my desktop. >>> >>> Alternative, I could probably create multiple shell users and switch >>> between each or do some other magic like swapping config files, but it >>> would be nice just to switch between profiles just like we do in git >>> between branches from within CloudMonkey shell. >>> >>> Your input is welcome, >>> >>> Thanks >>> ilya >>>
