How are you supposed to manage(i.e MODIFY/UPDATE) service configuration files in a deployed cloud and its containers?

The latest documentation hardly says anything about the command kolla-ansible genconfig, but my successfully(?) deployed cloud(about 1 out of every 10 attempts), still doesnt have a policy.json file configured for keystone?! How can such an important file be missing? What else is missing that I have to add manually??

Should I run "genconfig"? What is its purpose? What about the reconfigure action?

What I was initially after was enabling domain-specific logic in horizon/dashboard, but I get the feeling that the r/w files in the containers /etc/openstack-dashboard/ are NOT used, since I can find a reference to

"Binds": [
                "kolla_logs:/var/log/kolla/:rw",
                "/etc/localtime:/etc/localtime:ro",
                "/tmp:/tmp:rw",
                "/etc/kolla//horizon/:/var/lib/kolla/config_files/:ro"
            ],

with "docker inspect", and in the HOST i have a /etc/kolla/horizon/ with additional files. I've been trying to read up on docker volumes and bind mounts, but I wish that kollas OWN documentation could at least say SOMETHING about how I reconfigure a service and restart with that new service configuration?

I was thinking about using the /etc/kolla/config/ directory for deploying different settings for horizon, but wondering if this is supported for the local_settings file for horizon, since it doesn't follow the same syntax as the normal [Default]-type config files. And since I found the documentation saying:

As of now kolla only supports config overrides for ini based configs. // Queens docs

But the simple question, if I just want to change a simple .conf files, or add the policy.json file to keystone, WHERE should I add it, and what commands should I run, to integrate/activate it, into what I assume would be a restarted container?

Surely I cant be the FIRST to want to do this?!? TQ