Describe the bug
The schemachange dry run is used as a check before the actual implementation run to display the order of execution of the change scripts.
To Reproduce
Steps to reproduce the behavior:
Run a schemachange command using '--dry-run' parameter at the end.
Expected behavior
We would expect the Snowflake account details to be printed, scripts that would execute and NOT statements like ' Applying change script A__grant_permissions.sql ' as seen in the attached screenshot.
Screenshots
Schemachange:
Version: 3.6.1
Additional context
As seen I'm trying to run a dry run of a schemachange command using change scripts(version, repeatable, always).
It would be very helpful and informative if the output of dry run is cleaned up, and doesn't show statements like ' Applying script xyz ' as it isn't actually applying any change scripts at this point of the dry run and hence it is misleading and confusing.
Please let me know if you require additional details. Thank you.
Describe the bug The schemachange dry run is used as a check before the actual implementation run to display the order of execution of the change scripts.
To Reproduce Steps to reproduce the behavior: Run a schemachange command using '--dry-run' parameter at the end.
Expected behavior We would expect the Snowflake account details to be printed, scripts that would execute and NOT statements like ' Applying change script A__grant_permissions.sql ' as seen in the attached screenshot.
Screenshots
Schemachange:
Additional context As seen I'm trying to run a dry run of a schemachange command using change scripts(version, repeatable, always). It would be very helpful and informative if the output of dry run is cleaned up, and doesn't show statements like ' Applying script xyz ' as it isn't actually applying any change scripts at this point of the dry run and hence it is misleading and confusing.
Please let me know if you require additional details. Thank you.