Multischema configuration does not support environment variables

When attempting to use an environment variable to configure the schemas array in the datasource, OR the @@schema for models, the following error occurs:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Schema validation error - Error (query-engine-node-api library)
Error code: P1012
error: Expected a string value, but received functional value `env("DATABASE_SCHEMA")`.
  -->  schema.prisma:10
   | 
 9 |   url      = env("DATABASE_URL")
10 |   schemas  = [env("DATABASE_SCHEMA"), "public"]
   | 

Validation Error Count: 1
[Context: getConfig]

[aaron-henselin]

Exactly. In this use case, schema is really treated as a part of the environment/connectionstring rather than the application.

[aaron-henselin]

In this case, Heroku Connect, which uses the database as a formal pass-through into Salesforce. A Heroku Connect connected database can have “copies” of the same tables which direct the bidirectional replication, each in its own schema. So instead of a traditional “app1” / “app2” schema, it’s a “dev” / “production” schema. Is there a workaround or better way you can think of to accommodate this?