Liquibase tables need to be initialize for existing OTK DB. This is controlled using a property 'changeLogSync' true/false. Note that the OTK db need to be manually upgraded in this release (or the release when the switch to helm based DB upgrade is done) and from the next OTK upgrade this flag should be set to false so that OTK DB is upgraded.
Also, moved dbUpgrade and useDemoDb to otk.database.
Benefits
Customers can use existing OTK db for upgrade.
Drawbacks
N
Applicable issues
fixes #
Additional information
Checklist
[] Chart version bumped in Chart.yaml according to semver.
[] Variables are documented in the README.md
[] Title of the PR starts with chart name (e.g. [charts/gateway])
[] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
Description of the change
Liquibase tables need to be initialize for existing OTK DB. This is controlled using a property 'changeLogSync' true/false. Note that the OTK db need to be manually upgraded in this release (or the release when the switch to helm based DB upgrade is done) and from the next OTK upgrade this flag should be set to false so that OTK DB is upgraded.
Also, moved dbUpgrade and useDemoDb to otk.database.
Benefits Customers can use existing OTK db for upgrade.
Drawbacks N
Applicable issues
Additional information
Checklist
Chart.yamlaccording to semver.[charts/gateway])values-production.yamlapart fromvalues.yaml, ensure that you implement the changes in both files