Custom Parameter Values Corrupt Computed Changeset Checksum

I created a changelog file containing a changeset that inserts a record into a table with custom values passed in on the command line. For instance, I’d pass a parameter to execute liquibase from the command by specifying the custom parameter by including 


Is is expected behavior for the checksum to be based on the value after replacing ${param} because the SQL that was executed was different than what would be computed now. I created to track the feature to control that.

You can disable checksum validation by using a any tag.


Ah. I missed that attribute in the documentation somehow. Thank you for pointing that out.