-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Properties are not being substituted #4129
Comments
Came here while debugging the same issue. Some more info: Works when specifying properties on the command line as The failure affects both the SQL generated (as evidenced by |
Version 4.21.1 is also affected. Liquibase throws the exception |
Same with 4.21.1 and postgresql 14, parameters are not substituted when coming from Working after rollback to 4.20.0. |
It's only when you are setting properties from the |
I haven't tested all the other methods, I can only say that it works when setting the property via spring-boot with |
I validated the fix for this issue using a changelog that has changesets that use parameters defined in the changelog, parameters defined in the liquibase.properties file and a table that uses a combination of changelog and liquibase.properties parameters. I tested using the CLI against a Postgres 12.6; the Liquibase build is https://github.com/liquibase/liquibase/actions/runs/4874060226. In all cases, the correct substitution was executed using the fix build. The Changelog (liquibase.properties values listed in comment)
Thank you for submitting this issue, @joserebelo! |
Search first
Description
Properties are not being substituted when used on changes using the
${parameter}
format - they get passed to the changes as the literal string"${parameter}"
.git bisect tracked the issue to 6f8a113
Steps To Reproduce
Set a parameter on the defaults file:
Use the parameter on a change:
Expected/Desired Behavior
It was expected that a table with the name
"asd"
would have been created. However, a table with the literal name"${a_parameter}"
gets created.The same issue applies to args in the
executeCommand
change and params on customChanges.Liquibase Version
4.21.0
Database Vendor & Version
PostgreSQL 9.6
Liquibase Integration
cli
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: