Re: Juju API change - new ModelConfig facade

Thanks Ian, nice to see the change articulated clearly in advance with guidance as to how to accommodate it. Mark On 25/07/16 07:57, Ian Booth wrote: > In juju master, and landing with the next beta, 3 methods are moved off the > Client facade and now exist on a new ModelConfig facade: > > -

No help Topics in 2.0

Juju 1.x had a ton of help in the CLI, right at your fingertips: $ juju1 help topics azure-provider How to configure a Windows Azure provider basics Basic commands commandsBasic help for all commands constraints How to use commands with constraints

Re: Juju CLI change (status output)

Thanks for the warning. CI uses only YAML and JSON output, so it won't be affected. Aaron On 2016-07-26 11:01 AM, John Meinel wrote: > One tweak that is landing for the next 2.0 beta (14?) is to change 'juju > status' output to put PORTS after PUBLIC-ADDRESS. This is just alignment > with the

Juju CLI change (status output)

One tweak that is landing for the next 2.0 beta (14?) is to change 'juju status' output to put PORTS after PUBLIC-ADDRESS. This is just alignment with the fact that usually when you see it, it is 10.3.2.1:8080 not 8080 10.3.2.1 The particular PR is here: https://github.com/juju/juju/pull/5870 It

Re: Juju CI is updated to test the autoload-credentials changes

Thanks Curtis, appreciate the catch and the update. On Mon, Jul 25, 2016 at 6:34 PM Curtis Hovey-Canonical wrote: > We saw the autoload-credential test failures this morning. The test is > strongly coupled to the prompt text. We updated the test to support > the new text,