tripleo-heat-templates/deployment/heat
Alex Schultz 8e052715c8 Use kolla_config for other actions
Today for some services we mount in /var/lib/config-data/<service>/etc
which is actually an output from the container-puppet process. We should
be using kolla to ensure that we properly create the configurations
based on the puppet generated configurations and things in the
container.  Some services correctly leverage the kolla_config that the
associated api/service uses when running their db sync. This patch
aligns the rest to follow the similar pattern.

Change-Id: I0e3d5748a50937880a55413b75fe6eca479c9160
2021-06-02 08:34:05 -06:00
..
heat-api-cfn-container-puppet.yaml Merge "Cleanup optional flag for conf.modules.d" 2021-05-22 15:52:58 +00:00
heat-api-cloudwatch-disabled-puppet.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
heat-api-container-puppet.yaml Merge "Cleanup optional flag for conf.modules.d" 2021-05-22 15:52:58 +00:00
heat-base-puppet.yaml Use server side env merging for ServiceNetMap/VipSubnetMap 2021-05-19 10:16:58 +05:30
heat-engine-container-puppet.yaml Use kolla_config for other actions 2021-06-02 08:34:05 -06:00