Comment 7 for bug 1797229

Just to add a few notes:

* From what I see, Apache is being restarted on config updates. Maybe that's just in the current upstream; I'm not sure. However, it does seem to be restarting properly on the shared-db-relation-changed hook.

* The above proposed fix doesn't do anything about stale entries being left in keystone.conf after the shared-db relation is broken; however, the config will be correctly updated when the relation is re-established. My guess is that this might generally be good enough, but in case we wish to have the config revert to its original DB connection line, I've opened a separate ticket for that: https://bugs.launchpad.net/charm-keystone/+bug/1817362