[ANN] juju-core 1.9.4 has been released

[David Cheney]

That is correct.

The plan of record is to accept, but ignore, that key for the ec2 provider.

https://bugs.launchpad.net/juju-core/+bug/1074025

Cheers

Dave

On 18/12/12 08:34, Clint Byrum wrote:
> Excerpts from Kapil Thangavelu's message of 2012-12-17 12:18:52 -0800:
>> On Mon, Dec 17, 2012 at 2:10 PM, Clint Byrum <clint at ubuntu.com> wrote:
>>
>>> Excerpts from David Cheney's message of 2012-12-15 16:52:21 -0800:
>>>> juju-core 1.9.4
>>>> ===============
>>>>
>>>> A new experimental release of Juju, juju-core 1.9.4, is now available
>>>> for testing. This is an early release of the Go port of Juju and should
>>>> be considered experimental.
>>>>
>>>> Getting Juju
>>>> ------------
>>>>
>>>> juju-core 1.9.4 is available from the Gophers PPA
>>>>
>>>> https://code.launchpad.net/~gophers/+archive/go
>>>>
>>>> New and Notable
>>>> ---------------
>>>>
>>>> This release includes several improvements
>>>>
>>>> * juju-core now respects the default-series configuration key to control
>>>> the release series of the target environment.
>>>> * juju-core now supports all EC2 regions. Please raise a bug on the
>>>> juju-core project if you experience an issue using juju-core with the
>>>> EC2 provider.
>>>>
>>>> Known bugs and limitations
>>>> --------------------------
>>>>
>>>> As this is an early release of Juju in Go there are a number of features
>>>> which are still to be implemented. A non exhaustive list of known issues
>>>> is as follows.
>>>>
>>>> * EC2 is the only supported provider.
>>>> * Raring series environments are not supported.
>>>> Most types of relations are supported, but they are not displayed in
>>>> juju status. #1073966
>>>> * The ssl-hostname-verification configuration key is not valid in an
>>>> environments.yaml configuration. The EC2 provider does perform ssl host
>>>> verification by virtue of only talking to https endpoints. As a
>>>> temporary measure, please remove this key from your environments.yaml.
>>>> #1074025
>>>
>>> FYI, the point of this key is not to turn it on. It should ALWAYS
>>> default to on, and was only defaulted to off for one release to not
>>> break backward compatibility.
>>>
>>> The point is to be able to turn it off for private cloud/testing/etc.
>>>
>>
>> also "The EC2 provider does perform ssl host
>>> verification by virtue of only talking to https endpoints"... talking ssl
>> doesn't verify a cert by virtue of using ssl.
>
> Actually the go net/http library used in goamz does actually always
> verify certs.. it errors on expired certs, self signed, and wrong names.
>
> In fact, I was having a hard time figuring out how to turn that off
> before losing interest.
>