Support editing comments on a changeset after it has already been executed. Currently there's no way to update/correct a comment post-execution.
long-term
O
Orchid Condor
Able to edit comments in SQL files, but the current DBDevOps pipeline fails if comments are modified after a changeset has been applied.
Comments can be added or edited in a changeset even after it has been executed.
Editing comments should not trigger changeset re-execution or checksum validation, as comments are non-functional changes.
Currently, every comment modification requires manually recalculating the checksum and rerunning the pipeline.
This behavior was validated using a test changeset where the comment was edited after the changeset had already been executed.
Log In
S
Stephen Atwell
updated the status to
long-term
moving back to longterm. customer has clarified it is sql comments inside of a sql file referenced by a change set that they wish to be ignored.
S
Stephen Atwell
updated the status to
rejected
S
Stephen Atwell
I checked, and this is already supported. As long as the comment you are referring to is the 'comment' fiueld on the changeset (as opposed to, for example, editing a comment you have embedded inside the SQL being run by the changeset) than this works today.
If you are instead requesting being able to edit the sql embedded inside the changeset (even a comment in it) the option would be to use the validCheckSum: ANY functionality to disable making sure the changeset has not been modified.
Photo Viewer
View photos in a modal
S
Stephen Atwell
updated the status to
long-term
will consider adding this in the long term. Today you can do this by permitting the entire changeset to be edited by adding validCheckSum: ANY to its definition.
If you want all changes to always ignore checksums, you can do this by running the 'liquibase command' step before your apply command with the 'clear-checksums' command.
in both cases those will allow any part of the change to be updated after deployment, which increases the odds of drift between the desired state and current state.
O
Orchid Condor
Stephen Atwell Does this fix work for Liquibase formatted SQL as well?