Comment 2 for bug 1692317

There is a dedicated puppet module [1] to be called for generating a
specific client MySQL configuration which controls client bind address
and SSL connection. It is not being used yet in containers.

We could update all the services to include this puppet module during
the puppet config step, but in this case, if one needs to change this
file during minor updates, all services need to regenerate their
config, which I believe will cause outage.

The other solution I see is to generate the configuration file in its
dedicated location /var/log/config-data/mysql_client, and let all
services bind mount it. This way, config file change during minor
update will be taken into account at next service restart.

Any thought on that approach?

[1] /var/lib/config-data/mysql_client/etc/my.cnf.d/tripleo.cnf