How to mark changes as "fake" in sqitch?

[lorddaedra]

Hello!

I have 4 environments: PROD, STAGE, DEV and a local dev.
I use PostgreSQL 15 for all of them.

I've created several changes:

core/0001_initial
core/0002_prod_to_stage (depends on core/0001_initial)
core/0003_stage_to_dev (depends on core/0002_prod_to_stage)
core/0004_add_tables_for_some_feature (depends on core/0003_stage_to_dev)
(I'm going to add support for modules so I'll add later changes like module01/0001_initial)

I need

• mark core/0001_initial as deployed ("fake deploy" without actual deploy) on PROD, STAGE and DEV (add values to sqitch.changes and sqitch.events)
• mark core/0002_prod_to_stage as deployed ("fake deploy" without actual deploy) on STAGE and DEV (add values to sqitch.changes and sqitch.events)
• mark core/0003_stage_to_dev as deployed ("fake deploy" without actual deploy) on DEV (add values to sqitch.changes and sqitch.events)

I'm looking for something like --fake or --fake-initial (https://docs.djangoproject.com/en/5.1/ref/django-admin/#cmdoption-migrate-fake-initial).

Maybe I can manually insert data in sqitch.changes and sqitch.events tables for these changes.

Questions:

1. How to generate change_id and script_hash values?
2. But these tables and schema do not exists before first deploy so how to create schema without using deploy command? (Please, check sqitch upgrade should create schema if not exists #870 )

I would like to have the same sqitch.plan for all environments of the same customer (because of later I will add complexity by adding one or several modules and will generate different sqitch.plans for different customers with different set of module's changes so it may become too complex for me to maintain it)

[theory]

I think --log-only is what you want. See it under Options. To deploy for each environment:

PROD

sqitch deploy --log-only core/0001_initial
sqitch deploy

STAGE

sqitch deploy --log-only core/0002_prod_to_stage
sqitch deploy

DEV

sqitch deploy --log-only core/0003_stage_to_dev
sqitch deploy

Depending on your database engine, you might also be able to use variables passed with --set or target.$target.variables (via the target command) for each target and use them for conditional execution in your deploy and revert scripts.

[lorddaedra]

David, thank you for your reply!

I like Sqitch (I'm glad I chose it over dbmate) and will definitely try to explore all its features, variables can be very useful