Support Prisma SHADOW_DATABASE_URL

[chelkyl]

Rationale: When using shadow databases, you must use the shadowDatabaseUrl API field per the Prisma documentation.

Implementation: We supported passing DatabaseConfig.shadowDatabaseUrl in the Keystone config object.

Relevant Links:

• Do not fail on missing/empty shadow database URLs prisma/prisma-engines#1672

Follow-up From:

• feat: support prisma SHADOW_DATABASE_URL #6982

[changeset-bot]

🦋 Changeset detected

Latest commit: d906a85

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
@keystone-6/core	Minor
@keystone-6/auth	Major
@keystone-6/cloudinary	Major
@keystone-6/fields-document	Major
@keystone-6/session-store-redis	Major
@keystone-6/example-auth	Patch
@keystone-6/examples-app-basic	Patch
@keystone-6/example-ecommerce	Patch
@keystone-6/example-graphql-api-endpoint	Patch
@keystone-6/example-roles	Patch
@keystone-6/example-testing	Patch
@keystone-6/example-with-auth	Patch
@keystone-6/sandbox	Patch
@keystone-6/website	Patch
@keystone-6/example-document-field	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/9v27Gr41L19qEPYucNwfuLy3RR1t
✅ Preview: https://keystone-next-docs-git-fork-chelkyl-support-p-b08035-keystonejs.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d906a85:

Sandbox	Source
@keystone-6/sandbox	Configuration

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Jun 23, 2022 at 3:54AM (UTC)

[jlarmstrongiv]

@dcousens thanks for running the pipeline!

@bladey we’ve double checked the GraphQL schema updates #6982 (comment)

@molomby we implemented your suggestions from #6982 (comment)

Thank you all for your help! Let me know if there’s anything else needed to move this PR along.

[jlarmstrongiv]

@dcousens any updates? 🤞

[dcousens]

Hi @jlarmstrongiv, we haven't forgotten this, the only remaining block is to verify the desired behaviour around the schema.prisma changes.

We want to see if we can always provide the shadow database URL, and hoping that, it being blank reverts to the default behaviour.

[jlarmstrongiv]

Thanks for the update @dcousens much appreciated 👍

Yes, we implemented it similar to prisma flags

[borisno2]

Hi @jlarmstrongiv Thanks for your reply, we are wanting to avoid the prisma.schema file changing depending on environment variables.

If you were to alway print url = env("DATABASE_URL") shadowDatabaseUrl = env("SHADOW_DATABASE_URL") in the prisma schema but process.env.SHADOW_DATABASE_URL was blank does it just revert back to default behaviour? I assume due to prisma/prisma-engines#1672 if we also print shadowDatabaseUrl = env("SHADOW_DATABASE_URL") in the prisma.schema and the env is blank prisma will still be happy.

Let me know if you have any questions.

[jlarmstrongiv]

@borisno2 Thank you for following up! Oh I see, theoretically yes.

Back in February, the prisma/prisma-engines#1672 was recently merged and KeystoneJS was depending on an older version of prisma, so that was not possible at the time.

Now, with KeystoneJS depending on prisma@3.14.0 (released a month ago), including shadowDatabaseUrl = env("SHADOW_DATABASE_URL") in every schema should work.

[jlarmstrongiv]

@borisno2 we updated the PR with your suggestions 🚀 would you run the the workflow?

[jlarmstrongiv]

Interesting! We now set it to an empty string instead, which should work https://github.com/prisma/prisma-engines/pull/1672/files#diff-c1428df746767db7244ee782e01a8c5cd941e55218ee25ace07da1eece5907e7R169

Would you re-run the workflow @borisno2 ?

[jlarmstrongiv]

@borisno2 fixed some hard-coded schema tests, let’s try again 🚀 another workflow re-run?