RFC: prisma migrate commit sounds amazing

native support for different environments e.g. dev / canary / staging / production - for different database admin connection URLs etc

currently have to do various gymnastics with env vars / dotenv files per environment before running prisma CLI commands (migrate, studio) - using mess of unruly package.json scripts as shorthand

much nicer to be able to do e.g. npx prisma migrate:deploy --env staging or npx prisma studio --env development etc

would then unlock adding per-environment restrictions/safeguards e.g. disallow migrate reset for staging / production environments

A full database reset seems to happen any time data needs deletion, even in cases where the deletion will not affect other tables. It would be great to minimize resets.

Before continuing, the CLI would warn you when a full database reset was required and why

Allow Prisma to use Bun. My application runs on Bun, but I must have Node installed if I want to use the CLI.

I think better revert command

when i use npx prisma migrate dev --name xx --create-only i can't rollback/delete this migration if i don't need before dev/deploy.
i suggest add prisma migrate dev --name xx --create-rollback to complete this function @nikolasburk

rds proxy full support