I have an API that I'm deploying via the serverless framework. The problem I'm running into is that my RDS instance cannot be accessed outside of the VPC that cloud formation sets up by default. Unless I create a bastion host within the same security group I can't connect from my development machine or CI pipeline to run the initial (or any) migration. It seems like a huge hassle. Is there a better way to execute a Prisma migration from within an a lambda to avoid all of the additional tooling? If so I could just invoke a cloud function to execute any migrations to production.

Hey Jim 👋 , Welcome to Prisma's Slack!

prisma migrate

needs an interactive environment for execution. Currently we don't support non-interactive environments. However we are actively considering adding a

--allow-non-interactive

flag to support calling prisma migrate programatically. Here is the GitHub Issue which monitors progress for adding non-interactive flag. Can you please leave a 👍 to the issue and comment your use case, this would help our product and engineering team in prioritising the issue.

Will do! Thanks @Nurul

Hey Jim, This blog post of using Prisma Migrate with AWS Aurora Serverless might be of interest to you, it's not exactly what you need but definitely worth having a look.