--validCheckSum not taking

General Discussion
1

Hello,

I have an existing changeset in a SQL formatted changelog. Looks like this:

--liquibase formatted sql

--changeset my.name:dev-1.0.0 label:dev-v1 context:dev
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;

-- --changeset my.name:qa-1.0.0 label:qa-v1 context:qa
-- --comment: a comment
-- USE ROLE MY_ROLE;
-- USE SCHEMA MY_QA_SCHEMA;
-- CREATE STAGE IF NOT EXISTS my_qa_ext_stage
--     URL = 's3://a-bucket'
--     STORAGE_INTEGRATION = AN_INTEGRATION;

I was preparing for future changeset’s and mis-commented them. Now I’m trying to make a change to those so they are seen as actual changesets and get a checksum error as expected:

schemas/external_stages.sql::dev-1.0.0::my.name was: 8:de3b6d85303c32f2d212c69ae2b601e7 but is now: 8:d6e7640ccc986b9a7c8956e6c61be12a

So I take that checksum and add a --validCheckSum value but it still gives the same checksum error. Here is my attempt:

--liquibase formatted sql

--changeset my.name:dev-1.0.0 label:dev-v1 context:dev --validCheckSum: 8:d6e7640ccc986b9a7c8956e6c61be12a
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;

--changeset my.name:qa-1.0.0 label:qa-v1 context:qa
--comment: a comment
-- USE ROLE MY_ROLE;
-- USE SCHEMA MY_QA_SCHEMA;
-- CREATE STAGE IF NOT EXISTS my_qa_ext_stage
--     URL = 's3://a-bucket'
--     STORAGE_INTEGRATION = AN_INTEGRATION;

What am I doing wrong?

Note that the change on the 2nd changeset line for qa-1.0.0 and the subsequent comment is removing the leading -- .

Running v4.18.

2

Seems like the extra context isn’t really warranted as any change I make doesn’t seem to use the --validCheckSum value I provide or the special 1:any value. Is this a pro only feature? Is my only recourse to manually delete rows from the databasechangelog table?

3

Your formatting is incorrect. The – attributes need to be on their own line:

--changeset my.name:dev-1.0.0 label:dev-v1 context:dev 
--validCheckSum: 8:d6e7640ccc986b9a7c8956e6c61be12a
--comment: a comment
USE ROLE MY_ROLE;
USE SCHEMA MY_DEV_SCHEMA;
CREATE STAGE IF NOT EXISTS my_dev_ext_stage
    URL = 's3://a-bucket'
    STORAGE_INTEGRATION = AN_INTEGRATION;
2 Likes