Move barbican's database creation to mysql profile
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Tue, 15 Aug 2017 16:52:07 +0000 (19:52 +0300)
committerEmilien Macchi <emilien@redhat.com>
Thu, 17 Aug 2017 05:24:49 +0000 (05:24 +0000)
commit6b0c04a4720036828ffc5e8ea690fdeddc1a77fb
tree9f597f5521f7063ae5ba6ec9aa876438597ba461
parentc82a5fe7e0d6347b317505b2dd49d8b1d3fa8163
Move barbican's database creation to mysql profile

This makes sure that the database creation is only executed on the mysql
profile (or container if that's enabled), and stops the conflicts and
errors that were happening when barbican was deployed in containerized
environments.

Change-Id: Ib5c99482f62397fc5fb79a9dc537dfb06ee7f4df
Closes-Bug: #1710928
manifests/profile/base/barbican/api.pp
manifests/profile/base/database/mysql.pp
spec/classes/tripleo_profile_base_barbican_api_spec.rb