Re: Renaming of environments

On Fri, Oct 23, 2015 at 3:32 PM John Meinel wrote: > We can put the environment name in a field that is visible, but isn't > canonical. It depends on the specific use case, but if we can use tags, we > can use "juju-environment-uuid" or some tag like that as the official

Re: Renaming of environments

That's interesting Andrew and not something considered in the conversations around this so far. With the new Azure provider and resource groups is the name of that group mutable? For Azure at least the resource groupings should help with the tags/identification though it does complicate things for

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

bzr has a similar feature, but the problem with such a feature is that it can break scripts that expect the normal behaviour. That's why bzr provides a --no-aliases option, which all scripts calling bzr should use. The same applies to Juju. If "status" gets defaulted to "status

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Awesome!! \o/ As a big fan of aliases (bash, git, etc.) I'd start using this right away with juju now! :) Thanks Tim! Dimiter On 23.10.2015 07:12, Tim Penhey wrote: > Hi folks, > > I scratched a personal itch yesterday and added the ability for >

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

On 23 October 2015 at 05:12, Tim Penhey wrote: > Hi folks, > > I scratched a personal itch yesterday and added the ability for users to > specify their own aliases for juju commands. > > There are two primary use cases that I was trying to address. > > Firstly, the

New feature in 1.25.0: Payload Management!

Hey All, Moonstone have been working hard this cycle on delivering a way to manage payloads from within a Juju Charm, and providing a nice way to expose information about the payloads through the Juju client. We got off course for a bit there, but with the help of Mark and some others, we're