Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
added cloud config database entities
added cloud config repository
converted existing cloud config class
converted all code interacting with previous cloud config object
created migration to automatically load cloud config properties from
application.yaml
Issue-ID: SO-854
Change-Id: Icf408e5d0fcabd1b7e97298963c555fae6964930
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|
|
Removed declaration of exception TenantAlreadyExists
since TenantAlreadyExists is a subclass of TenantException
which is declared earlier. Having TenantAlreadyExists is
superfluous since it is a subclass of another listed exception.
Issue-ID: SO-666
Change-Id: Ic828f4f18b865767bde7d34630f31683d7d49503
Signed-off-by: Anisha Kumar <anishax.kumar@intel.com>
|
|
Issue-ID: SO-729
Change-Id: I2b36cfdc706ea85e57e69dba569d026686065d3a
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
|
|
Issue-ID: SO-781
Change-Id: Ia91a52692e61f1ffa3f0a4074017fa0156d4276c
Signed-off-by: Smokowski, Steve (ss835w) <ss835w@us.att.com>
|
|
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18
Issue-ID: SO-670
Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
|