Merge lp:~jjo/juju-deployer/diff-usability-fixes into lp:juju-deployer
Status: | Merged |
---|---|
Merged at revision: | 89 |
Proposed branch: | lp:~jjo/juju-deployer/diff-usability-fixes |
Merge into: | lp:juju-deployer |
Diff against target: |
125 lines (+39/-20) 5 files modified
deployer/action/diff.py (+14/-9) deployer/env/go.py (+1/-1) deployer/tests/test_data/blog-haproxy-services.yaml (+14/-0) deployer/tests/test_data/blog.yaml (+9/-9) deployer/tests/test_deployment.py (+1/-1) |
To merge this branch: | bzr merge lp:~jjo/juju-deployer/diff-usability-fixes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
juju-deployers | Pending | ||
Review via email:
|
Commit message
* action/diff.py:
- create an output-less do_diff() method, to be used to implement
unit-tests
- add more detail to diff output re: values coming from cfg or env.
Rationale: after seeing a config diff, one usually then goes for a
juju get <svc_name> to find the env config value, which is a non-sense
workflow given that we do know its current value.
Ditto constraints.
* tests/test_data/:
- fix blog.yaml: proper indentation for memcache,haproxy (so that they're
actually parsed as services).
- add blog-haproxy-
(instead of nonexistent blog-include.yaml).
* tests/test_
for wider coverage.
To ease/minimize this review, lp:~jjo/juju-deployer/diff-usability-fixes_and_diff-tests is stacked over this.