lp://qastaging/~johnsca/juju-deployer/fallback
- Get this branch:
- bzr branch lp://qastaging/~johnsca/juju-deployer/fallback
Branch merges
- Tom Haddon: Abstain
- juju-deployers: Pending requested
-
Diff: 102 lines (+49/-0)3 files modifieddeployer/charm.py (+10/-0)
deployer/tests/test_charm.py (+33/-0)
deployer/tests/test_data/stack-placement.yaml (+6/-0)
Branch information
Recent revisions
- 160. By Cory Johns
-
Allow charm specification with no prefix to fall back to store if not found locally
- 154. By Tim Van Steenburgh
-
[frankban] Allow deploying bundles with v4 syntax from the GUI server/API
side of deployer.Also fix the add_unit logic in the importer so that the expected result
(of adding one single unit) is achieved also when using the juju-core API
(GUIEnvironment) for deploying charms. - 152. By Tim Van Steenburgh
-
[frankban] Fix deployments of bundles v4.
Fix some incorrect behavior of new v4 bundles, mostly
concerning validation and ordering of services.Improve status retrieval while adding unit.
Fix checking for existing machines: it did work
properly only with top level machines.Fix a problem with machines mapping while
co-locating units to other services, units or
to declared machines.Improve the logic used for detecting v4 vs v3
bundle syntax: the machines section in v4 can
be safely omitted accotding to the spec.Fix sleep loops and memory leaks while running
tests exercising the importer.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/juju-deployer