With Prisma's current lack of rollbacks, is there a suggested method of handling this in production?

hey @Yaakov - we currently have a proposal out to address the need for rollbacks. Please take a look and leave a comment! https://github.com/prisma/prisma/issues/10561

Thank you!!

Why not “roll forwards”?

It supports also to roll forward :)

@Frederik Thank you for pushing Prisma ahead with your proposal! After reviewing the post as well as all the comments, I'm wondering how this can work with an automated process. Our goal is to have all tests, deployments and migrations handled by AWS CodePipeline, with the end result having ECS running the app in docker containers. Seems like your proposal is intended for manual operations and requires someone on standby to choose to go forward or backwards?

Hey Yaakov - apologies for the delay - yes that would be awesome!

Hey, @Yaakov, the proposed commands are now available in 3.9. Here is a guide how to use them. We'd love to get some feedback on that solution. https://www.prisma.io/docs/guides/database/production-troubleshooting#new-commands-migrate-diff-and-db-execute