Merge lp:~cjwatson/charms/trusty/turnip/build-label into lp:~canonical-launchpad-branches/charms/trusty/turnip/devel
Status: | Merged |
---|---|
Merged at revision: | 81 |
Proposed branch: | lp:~cjwatson/charms/trusty/turnip/build-label |
Merge into: | lp:~canonical-launchpad-branches/charms/trusty/turnip/devel |
Diff against target: |
491 lines (+209/-72) 12 files modified
.bzrignore (+1/-2) Makefile.common (+24/-21) README.md (+0/-2) config.yaml (+28/-0) deploy-requirements.txt (+0/-2) hooks/actions.py (+149/-38) hooks/services.py (+2/-2) templates/turnip-httpserver.conf.j2 (+1/-1) templates/turnip-packbackendserver.conf.j2 (+1/-1) templates/turnip-packfrontendserver.conf.j2 (+1/-1) templates/turnip-sshserver.conf.j2 (+1/-1) templates/turnip-virtserver.conf.j2 (+1/-1) |
To merge this branch: | bzr merge lp:~cjwatson/charms/trusty/turnip/build-label |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Kit Randel (community) | Approve | ||
Review via email: mp+275468@code.launchpad.net |
Commit message
Allow updating the code payload separately from the charm using a build label.
Description of the change
Allow updating the code payload separately from the charm using a build label.
The approach used here is based heavily on the software-
The virtualenv moves inside the payload directory so that each payload gets its own. /srv/turnip/code remains as a symlink to the current payload, which is convenient and saves us having to substitute the current build label into the Upstart jobs.
There are no tests directly here, but it'll at least get integration testing by way of the corresponding changes to the Mojo spec.
Just a minor formatting issue.
I'm working through updating Rutabaga's charm similarly as a somewhat circumlocuitous form of review. No doubt fine, given the mojo spec ran, but thought it might be worth leaving this open in the event that I came across anything in the process.
Given our services will be duplicating a reasonable amount of charm code, I did wonder if we should consider maintaining our own charmhelpers like library.