dbms in preConditions yaml changelog causes parsing error

Description

I've replicated this issue:

  1. running the following Liquibase command line (close to the bottom of this description) with the attached zip of the liquibase-3.5.1-bin.zip tools from Liquibase

  2. in my spring-boot application.


Both have the same yaml parsing error. I've paired down my yaml file to the main error which seems to be the usage of dbms in preConditions for a createSequence. See my yaml files in the attached .zip file in the .\db\changelog folder - initial.yaml.

This yaml worked fine in Liquibase core 3.3.5 which my product is currently using.

I picked up a story to upgrade to Liquibase core 3.5.1, but this parsing error is blocking my story.

Liquibase 3.5.1 bin tools command used:
liquibase --logLevel=info --logFile=logs/logs.txt --driver=org.postgresql.Driver --changeLogFile=db/changelog/db.changelog-master.yaml --classpath=postgresql-9.3-1100-jdbc41.jar --url="jdbcostgresql://localhost:5432/msa_lpm" --username=postgres --password=password update

See the /logs folder for the parsing error log output.

Environment

Windows 2008 R2 Server
Using a Postgres 9.4.7 DB ... but the yaml parse error is the main issue - database should not matter.
Java 1.8.0_60-b27 64-bit

Attachments

1

Activity

Show:

Nathan Voxland 
July 27, 2016 at 10:03 PM

Fixed, thanks for the example changelogs

MikeL 
May 19, 2016 at 6:37 PM

I just tried my spring boot app build with liquibase-core 3.4.2 and then 3.5.0:

  • 3.4.2 did not have the parsing error

  • 3.5.0 did have the parsing error

Fixed

Details

Reporter

Components

Fix versions

Affects versions

Priority

Created May 19, 2016 at 3:38 PM
Updated July 27, 2016 at 10:03 PM
Resolved July 27, 2016 at 10:03 PM