Problems with custom change's confirmation message when using parameters
Description
When running dbDoc a custom change properties are set when CustomChangeWrapper.validate is called. But since PR #88, already ran changes are no longer validated (for performance reasons). Unfortunately that causes problems if the properties are used in composing the confirmation message (from NPEs - causing dbDoc to fail - to wrong messages - nulls everywhere).
Proposed fix (in https://github.com/liquibase/liquibase/pull/634) is to configure change before calling getConfirmationMessage, hence doing the minimum needed and avoiding (potentially) expensive revalidation of custom changes.
Environment
OS and DB independent, triggered through the CLI or Maven plugin.
When running dbDoc a custom change properties are set when CustomChangeWrapper.validate is called. But since PR #88, already ran
changes are no longer validated (for performance reasons). Unfortunately that causes problems if the properties are used in composing the confirmation
message (from NPEs - causing dbDoc to fail - to wrong messages - nulls
everywhere).
Proposed fix (in https://github.com/liquibase/liquibase/pull/634) is to configure change before calling getConfirmationMessage, hence doing the minimum needed and avoiding (potentially) expensive revalidation of custom changes.