Consolidate bundle rendering
Bug #1605641 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Charm |
Fix Released
|
Medium
|
Andreas Hasenack | ||
Bug Description
We have these two branches nowadays:
lp:~landscape/landscape-charm/bundles-trunk
lp:~landscape/landscape-charm/bundles-stable
The stable version is meant to reflect what is in the store.
Currently the "make render" command has a different behavior in trunk. Bundles are rendered in a build/<target> subdirectory, always named bundle.yaml, whereas in stable they are rendered in the current directory and named after each target.
We want the trunk behavior to be reflected in stable so system tests can use either and expect just one output format structure.
At this time, we do not want the actual bundle to be changed: i.e., stable should remain trusty, with the same charm revisions.
Related branches
lp:~ahasenack/landscape-charm/new-bundle-render
- Francis Ginther (community): Approve
- 🤖 Landscape Builder: Approve (test results)
- Ursula Junque (community): Approve
-
Diff: 466 lines (+182/-207)9 files modified.bzrignore (+1/-0)
Makefile (+21/-10)
charm-store (+68/-21)
landscape-dense-maas.yaml (+0/-59)
landscape-dense.yaml (+0/-59)
landscape-scalable.yaml (+0/-49)
render-bundles (+25/-4)
ubuntu-deps (+62/-0)
update-charm-revisions (+5/-5)
| Changed in landscape-charm: | |
| status: | In Progress → Fix Committed |
| Changed in landscape-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
