If the charm switches the service from http to https (or vice versa)
and the default identity-service handler has already run during this
hook execution then keystone is not informed of the change until a
subsequant hook execution. This subsequant hook could be
update-status as the charm currently does not disable any of its
methods during update-status hooks.
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Ensure that openstack upgrades are triggered if the openstack-origin
configuration option is changed and configuration of the placement
service is complete.