Question about

prisma migrate

- was looking around for an option to do a 'dry run' of a migration before it's deployed, but didn't come across anything. Our goal is to be able to validate a migration in development against our production database(s) before that code is ever merged and deployed, so we don't have to wait for it to fail, then go through the process of rolling it back, editing the migration, re-deploying, etc..

Hello @Ty-Lucas Kelley 👋 If I understand correctly, could you create an environment identical to production having a subset of data and execute migrations on them? Maybe Snaplet could be useful for this scenario: https://www.snaplet.dev/

This would be a backup plan in the event there's no option for a dry run

@Ty-Lucas Kelley If I understand the use case correctly, you could try using

prisma migrate dev --create-only

. It will still run the migration validations using a shadow database, but it won’t apply the generated SQL.