tripleo-heat-templates/deployment/database
Emilien Macchi 7c2fa7b8e9 mysql: move firewall_rules to mysql-container-puppet
The firewall_rules need to be in the service template and can't be in
the base, that is imported.
The current YAQL is looking for firewall_rules in the role_data:
$.data.role_data, []).where($ != null).select($.get('firewall_rules')

So moving the firewall_rules from mysql-base to mysql-container-puppet
will allow the data to be found by the query and the firewall rules to
be applied.

Change-Id: I6183cdf63ea628cc86742d56b5e2cc0ec5e3aab9
Closes-Bug: #1856864
2019-12-18 10:47:31 -05:00
..
mysql-base.yaml mysql: move firewall_rules to mysql-container-puppet 2019-12-18 10:47:31 -05:00
mysql-client.yaml flatten database service MySQL Client 2019-01-30 09:38:32 -05:00
mysql-container-puppet.yaml mysql: move firewall_rules to mysql-container-puppet 2019-12-18 10:47:31 -05:00
mysql-pacemaker-puppet.yaml Merge "HA: minor update of arbitrary container image name" 2019-12-10 13:17:41 +00:00
redis-base-puppet.yaml Force redis::ulimit to be an integer 2019-11-27 17:08:32 +01:00
redis-container-puppet.yaml Remove unnecessary slash volume maps 2019-12-04 20:32:14 +02:00
redis-pacemaker-puppet.yaml Merge "HA: minor update of arbitrary container image name" 2019-12-10 13:17:41 +00:00