Merge lp:~tvansteenburgh/juju-deployer/abspath-charms into lp:juju-deployer
Proposed by
Tim Van Steenburgh
Status: | Merged |
---|---|
Merged at revision: | 150 |
Proposed branch: | lp:~tvansteenburgh/juju-deployer/abspath-charms |
Merge into: | lp:juju-deployer |
Diff against target: |
156 lines (+66/-5) 4 files modified
deployer/action/importer.py (+4/-3) deployer/charm.py (+32/-2) deployer/env/base.py (+6/-0) deployer/tests/test_charm.py (+24/-0) |
To merge this branch: | bzr merge lp:~tvansteenburgh/juju-deployer/abspath-charms |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Marco Ceppi (community) | Approve | ||
juju-deployers | Pending | ||
Review via email: mp+266329@code.launchpad.net |
Description of the change
Allow charms to be specified using an absolute local path.
For example:
services:
mycharm:
charm: /tmp/trusty/mycharm
Primary rationale for this is to allow rapid iteration on a charm's amulet
tests, without needing to commit the changes, or even have them under
revision control. For the charm under test, amulet will give deployer an
absolute path, ensuring that the version of the charm that is deployed and
tested is whatever is on disk at the time.
To post a comment you must log in.
+1 this will simplify a lot of tools and workloads for people!