Are dynamic Prisma (client) instances supported?

[tomi-bigpi]

Background:
We're using AWS RDS with IAM authentication which (currently, due to Prisma limitations) requires creating a new Prisma client every 15 minutes or so. We currently have an implementation where the context returns the "current" Prisma instance which is automatically (re)created when the authentication password expires.

Question:
Does Pothos cache the prisma instance given as options to SchemaBuilder and/or is there a way to make sure each time Prisma is needed that the latest instance is used to allow dynamically replacing the Prisma instance for this use case?

[hayes]

This is not currently supported, but would be easy to add

[tomi-bigpi]

Awesome, I'll keep an eye out on future releases.

[hayes]

just merged a change that allows you to dynamically get the prisma client on a per-request basis

[hayes]

updated docs here: https://pothos-graphql.dev/docs/plugins/prisma#set-up-the-builder

[tomi-bigpi]

Do you have a clean way to get the prisma.dmmf dynamically in mind?

When my builder.ts is imported, the Prisma instance is null since we need to create it asynchronously by first calling AWS for credentials etc. I'm currently looking at wrapping all builder.xxx calls in either functions or classes to control passing in the builder instance, but that's less clean that just doing import 'types/MyType.ts'.

[hayes]

You probably need to create a client with a fake connection url. I don't think prisma will create a connection until the client is used, so that should work fine