summaryrefslogtreecommitdiffstats
path: root/adapters/mso-openstack-adapters/src/main/resources/application-local.yaml
diff options
context:
space:
mode:
authorRob Daugherty <rd472p@att.com>2018-08-21 18:42:55 -0400
committerRob Daugherty <rd472p@att.com>2018-08-21 18:42:55 -0400
commit5bea41b162b9c4d6a24640790028fa7750ff15f3 (patch)
tree72f3853aa6bde8806e24ea86e89ccda448d53ddf /adapters/mso-openstack-adapters/src/main/resources/application-local.yaml
parent539776c6a387e25f0c428be1f8c6912d94c50e88 (diff)
openstack_adapter container fails to start
The reported problem occurs because the openstack-adapters app is attempting to do a migration on top of a migration already performed by the catalog-db app. I'm adding these options to flyway in openstack-adapters: baseline-on-migrate: true validate-on-migrate: false Another issue is that the java-based CloudConfig migration class was looking for CloudConfig data only in the application.yaml file in the classpath. It was not looking for CloudConfig data in the override file. I've changed this logic to look in the override file first and then in application.yaml. Ideally, these sources would be merged, but I don't see a reasonable way to do it. Change-Id: I7ba07c1f8f00b4c628e825393ee31502950fe592 Issue-ID: SO-868 Signed-off-by: Rob Daugherty <rd472p@att.com>
Diffstat (limited to 'adapters/mso-openstack-adapters/src/main/resources/application-local.yaml')
0 files changed, 0 insertions, 0 deletions