Merge lp:~johnsca/juju-deployer/fallback into lp:juju-deployer
Proposed by Cory Johns
| Status: | Rejected |
|---|---|
| Rejected by: | Haw Loeung |
| Proposed branch: | lp:~johnsca/juju-deployer/fallback |
| Merge into: | lp:juju-deployer |
| Diff against target: | 102 lines (+49/-0) 3 files modified deployer/charm.py (+10/-0) deployer/tests/test_charm.py (+33/-0) deployer/tests/test_data/stack-placement.yaml (+6/-0) |
| To merge this branch: | bzr merge lp:~johnsca/juju-deployer/fallback |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Tom Haddon (community) | Abstain | ||
| juju-deployers | Pending | ||
| Review via email: | |||
Commit message
Allow charm specification with no prefix to fall back to store if not found locally
Description of the change
If a service is specified with no prefix (neither cs: nor local:) and it doesn't exist locally, fallback to using the charm store. (Current behavior is to assume local and fail if it doesn't exist.)
To post a comment you must log in.
Unmerged revisions
- 160. By Cory Johns
-
Allow charm specification with no prefix to fall back to store if not found locally
To clarify: the changes to stack-placement .yaml were necessary because that bundle was depending on the previous behavior of defaulting to local charms and not trying the store, which was causing deployer/ tests/test_ deployment. py:DeploymentTe st.test_ validate_ placement_ sorting to fail, when it attempted to fetch the charms from the store.
The changes to the .yaml force it to consider them local charms and not try to fetch them, matching the expected behavior.