Merge lp://staging/~aisrael/charms/precise/glance/charm-proof into lp://staging/~openstack-charmers-archive/charms/precise/glance/trunk

This currently affects most charms and since this type of fix is functionally equivalent I reckon it would make more sense to adjust charm proof to ignore lack of default for string type.

Edward,

This is setting default as a None value, rather than an empty string, which would be "". It's simply lowering the output message to an informational one instead of an error. I believe it would not conflict with any of the current code.

Jose, if default: is omitted it has the same effect as if adding it with no value i.e. it produces None as the value of the config parameter (at least that is the behaviour I get with juju-core 1.20.7-0ubuntu1~14.04.1~juju1). So this change has no effect at all other than pacifying charm proof. As a result I think that charm proof should ignore the case where no default is provided since it is a false positive.

I agree with Edward. If it's possible to improve charm proof, that's the better approach rather than every single charm having to add useless lines to appease the tool. Anyway I can't reproduce this so maybe charm proof has already been updated?

The whole Ecosystem team is going through older charms increasing their quality to the agreed upon standard. Adding the default: field removes ambiguity for our users and is a good thing. Please voice your objections on the juju mailing list: <email address hidden> so it can be discussed with everyone concerned with Juju, rather than the few people subscribed to this bug report. The juju mailing list contains the people who can be convinced to change the tooling and policy if needed.

Equiv fix landed into /next, release in 2 wks.