Ensure using the correct 'public' API for charms.reactive (0.5.0.b* tag)

Bug #1718208 reported by Alex Kavanagh on 2017-09-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charms.openstack
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://github.com/juju-solutions/charms.reactive/issues/124 for details.

Changed in charms.openstack:
importance: Undecided → Medium
Cory Johns (johnsca) wrote :

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.

Alex Kavanagh (ajkavanagh) wrote :

Need to track this; the shims will eventually go away, probably should target this to a release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers