Merge ~cjwatson/launchpad-layers:payload-layer into launchpad-layers:main
Proposed by
Colin Watson
Status: | Merged |
---|---|
Merged at revision: | 72b0393e9d3d34e29aaeddec5787e13ac826b277 |
Proposed branch: | ~cjwatson/launchpad-layers:payload-layer |
Merge into: | launchpad-layers:main |
Diff against target: |
404 lines (+152/-102) 8 files modified
launchpad-base/config.yaml (+0/-11) launchpad-base/layer.yaml (+1/-11) launchpad-base/lib/charms/launchpad/base.py (+4/-46) launchpad-base/reactive/launchpad-base.py (+9/-34) launchpad-payload/config.yaml (+12/-0) launchpad-payload/layer.yaml (+17/-0) launchpad-payload/lib/charms/launchpad/payload.py (+66/-0) launchpad-payload/reactive/launchpad-payload.py (+43/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clinton Fung | Approve | ||
Guruprasad | Approve | ||
Review via email:
|
Commit message
Move part of launchpad-base into a new launchpad-payload layer
Description of the change
Some charms - at least the prospective `launchpad-assets`, which publishes CSS/JS etc. assets for use by frontends - only really need an unpacked Launchpad payload, and don't need the rest of `launchpad-base`. Extract that part into a separate layer.
To post a comment you must log in.
LGTM 👍🏼