Merge lp:~free.ekanayaka/landscape-charm/new-data-provider-flow into lp:~landscape/landscape-charm/trunk
Proposed by
Free Ekanayaka
Status: | Merged |
---|---|
Approved by: | Free Ekanayaka |
Approved revision: | 299 |
Merged at revision: | 299 |
Proposed branch: | lp:~free.ekanayaka/landscape-charm/new-data-provider-flow |
Merge into: | lp:~landscape/landscape-charm/trunk |
Diff against target: |
248 lines (+103/-37) 5 files modified
charmhelpers/core/hookenv.py (+62/-1) charmhelpers/core/services/base.py (+30/-9) charmhelpers/fetch/giturl.py (+7/-5) lib/services.py (+2/-16) lib/tests/test_services.py (+2/-6) |
To merge this branch: | bzr merge lp:~free.ekanayaka/landscape-charm/new-data-provider-flow |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
🤖 Landscape Builder | test results | Approve | |
Данило Шеган (community) | Approve | ||
Björn Tillenius (community) | Approve | ||
Review via email: mp+260936@code.launchpad.net |
Commit message
This branch syncs the charmhelper copy in the charm and takes advantage of some recent changes in the services framework, which now allow data-providers to be triggered outside relation hooks. We As a workaround we happened to have exactly the same behavior, which can now be dropped.
Description of the change
This branch syncs the charmhelper copy in the charm and takes advantage of some recent changes in the services framework, which now allow data-providers to be triggered outside relation hooks. We As a workaround we happened to have exactly the same behavior, which can now be dropped.
To post a comment you must log in.
+1