[Redwood.js] provider = "redwood"

Redwood wants to enable their users to use SQLite in dev, and Postgres in production. To enable that, they need some special logic:

• Redwood creates the schema with a (virtual) provider called redwood
• When calling Prisma commands, Redwood uses --schema to supply a dynamically generated version of the schema where redwood is replaced depending on the environment (with sqlite or postgres)

(Internal context: https://www.notion.so/prismaio/provider-redwood-fd04ffcc9c684a9bb5cdb5d5a5fc2ecc + https://prisma-company.slack.com/archives/CL0AJEVSA/p1580897189010000)

---

Tasks:

• Double check that --schema works for this
• Schema validator and VSCode (and whoever else looks at the provider) have to be happy about redwood
• (Optional) Our CLI could detect redwood specific stuff (like redwood) and point user to use it instead of Prisma directly (because directly we will not do the replacing things and stuff might break)

[janpio]

I think Redwood should already be able to fully build what they are aiming for, --schema works and if they call all the Prisma CLI commands with that behind the scenes, provider=redwood should never make it to Prisma CLI to fail this way.

We now have to decide where and how we want to either a) enable redwood as a valid value or b) fail with a nicer error message that tells people to use the Redwood CLI.

@schickling? Do we know what the Redwood.js CLI will look like that people should prefer using here?

Suggestion:

• Make redwood a ~~warning~ ~valid value in VS Code, and somehow point to Redwood in the description suggest that Redwood generates a comment next to it that links to an explanation how the replacing works
• Handle all the CLI/Engine cases with a error message, but fail anyway (as we can not really run the command without the real provider value)

[cannikin]

We got it! It looks like this is working for us, thanks so much!