1df85ff800
These where moved up to this layer from ``layer-openstack-api``, removal counterpart: I007275c041ca5465664a6b5d441e56c0316c405d Guard the default handlers behind check for 'charms.openstack.do-default-certificates.available' flag. This flag is activated when the consumer charm makes a call to charm.use_defaults('certificates.available') from its reactive handler. Previously it was always activated for all consumers of the ``openstack-api`` layer, it should be up to the charm implementation to choose. We do not add back ``layer-tls-client``, the reason being that the reactive bits in ``layer-openstack`` in conjunction with helpers in ``charms.openstack`` is managing both the server and CA certificates and rely on the same flags to detect changes. If we one day offload those tasks to the ``layer-tls-client`` we should add it back in conjunction with removing our code for this. At the time of this writing it would not be possible as ``layer-tls-client`` is not spaces aware. With the above mentioned change we can stop relying on the now deprecated ``certificates.batch.cert.available`` flag. We also do not add back the Keystone certificates handling code as this has been removed from the Keystone charm reference: openstack/charm-keystone/commit/17b24e7fde8e4c8c276a4f392cbae0d1d0ed2615 Needed-By: I007275c041ca5465664a6b5d441e56c0316c405d Needed-By: I8a72acd451dd21e1b042b7f71f6d98e164737ac1 Closes-Bug: #1840899 Change-Id: I12f45236632b608e07fdd35d31b90b84ca92eb1f |
||
---|---|---|
.. | ||
layer_openstack.py |