Ensure using the correct 'public' API for charms.reactive (0.5.0.b* tag)
Bug #1718208 reported by
Alex Kavanagh
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charms.openstack |
New
|
Medium
|
Unassigned | ||
Bug Description
charms.openstack, for historical reasons, uses some of the internal API functions of charms.reactive. With the 0.5.0.b* releases the internal API is changing due to the renaming of states to flags, amongst other things. This means that charms.openstack based charms won't build with charms.reactive >= 0.5.0.
charms.openstack ought to be using the 'proper' API, and if that's not 'powerful' enough, requesting appropriate changes in charms.reactive. Therefore, we need to factor out the offending code in charms.openstack.
See https:/
| Changed in charms.openstack: | |
| importance: | Undecided → Medium |
Revision history for this message
| Cory Johns (johnsca) wrote | #1 |
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #2 |
To post a comment you must log in.
The lack of backwards compatible shims / references was an oversight which has been corrected in the latest beta release, so the "won't build" should no longer be true. However, those shims / imports are deprecated so moving off of them would be best.