Prisma Migrate: Support for configuring the shadow DB URL

Problem

The migrate dev or migrate reset commands in Prisma Migrate require a shadow database. Prisma Migrate assumes the same credentials used for the development database can be used to create it. When using a local DBMS, this can be achieved by granting the user privileges to create new databases.

Some of our users develop on the cloud and don’t run their DBMS locally. This prevents these users from using Prisma Migrate in development unless they switch to using a local DBMS.

Solutions

We could allow users to provide a URL to a shadow database that can be used as the shadow database. Example: a user could provision two Postgres databases on Heroku, one for the development another the shadow database.

In order to do this, we’d need to enable a way to supply this configuration, i.e., config file, env variable, etc.

[albertoperdomo]

@perryraskin Unfortunately not, but hopefully we can release it in 2.16.0. Thanks for your patience while we figure out the best solution.

[albertoperdomo]

This feature is now live in 2.17.0 - https://github.com/prisma/prisma/releases/tag/2.17.0

For feedback, please post on https://github.com/prisma/prisma/issues/4531.