Hi team 👋 Does anyone know if the prisma client has some method to test if the current schema is valid? I'm using ECS to host my backend and the pipeline does

primsa migrate deploy

after the rollout of the pods. Before allowing users to consume the new pods of the API, ECS checks if these are healthy, in order to do that I usually define a simple endpoint at

/api/health_check

that returns 200 OK. Now, ideally the new pods shouldn't be considered "healthy" until their prisma client matches the deployed DB schema, is there a way to "health test" prisma inside my health check endpoint?

Hey Franco 👋 this is a really interesting question but unfortunately I don’t think this is possible at the moment with Prisma Client. Would you maybe mind opening a new feature request for this? I think it would be interesting for our Product and Engineering teams to evaluate this 🙂

Sure thing, will do!