Merge lp:~nextrevision/charms/precise/openvpn-as/trunk into lp:charms/openvpn-as
Proposed by
John Patterson
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 8 | ||||
Proposed branch: | lp:~nextrevision/charms/precise/openvpn-as/trunk | ||||
Merge into: | lp:charms/openvpn-as | ||||
Diff against target: |
31 lines (+4/-2) 2 files modified
config.yaml (+2/-0) hooks/install (+2/-2) |
||||
To merge this branch: | bzr merge lp:~nextrevision/charms/precise/openvpn-as/trunk | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Marco Ceppi (community) | Approve | ||
charmers | Pending | ||
Review via email: mp+201310@code.launchpad.net |
Description of the change
Updated the OpenVPN-AS package version to latest and removed the revision file.
To post a comment you must log in.
Hey John! Thanks for submitting this change and continuing to maintain the charm!
While this change looks fine, some new charm policies have been added since this was submitted to the store. Running `juju charm proof` from the charm-tools package (available in ppa:juju/stable) I get the following output:
W: config.yaml: option license does not have the keys: default
W: config.yaml: option fqdn does not have the keys: default
These are very minor and easily corrected warnings. Going forward all configuration options should have a default key, if the default is to be "empty" then just set it to the appropriate empty value for it's type. (IE: default for a string would be ""). Without these defaults, the charm may behave erratically in the juju gui.
Unfortuantely, as these are warnings, this is blocking the merge from being accepted.
Long story short, this LGTM and is a +1 as soon as the proof errors are resolved. As such, I've had to make this as "Needs Fixing", once you've addressed the above please select the "Request another review" button and request a review from "charmers". This will re-add your merge request to our review queue and we'll be able to re-test!
If you have any questions you can always reply here, join us in #juju on freenode.net, ask a question tagged juju on askubuntu.com, or send us an email <email address hidden>
Thanks again for your continued contributions!