Prisma1: prisma.yml can't use variable for disableAuth

[johnslemmer]

Current behavior

When trying to deploy a service using a .env that has variables used in prisma.yml. I get this error:

 ▸    Invalid prisma.yml file
 ▸    prisma.yml.disableAuth should be boolean. type: boolean

Reproduction

This branch of this repo will reproduce the issue.

https://github.com/johnslemmer/todos-db-prisma/tree/bug-prisma-disableAuth-variable

Expected behavior?

disableAuth should be able to be set using a variable. It currently can't.

[marktani]

I believe the problem is that are stating both disableAuth and secret in your prima.yml file. Could you try either of those?

[johnslemmer]

See my latest commit: https://github.com/johnslemmer/todos-db-prisma/tree/6f0df3dc55fc7bf3795a364f012a07c208d15799

I have tried commenting out secret and I'm still getting the same error.

Also, I think it would be desirable to be able to do the following in the future so that a .env file can control all aspects of deployment. I believe this would be a good feature for everyone (just based on https://12factor.net/).

stage: ${env:PRISMA_STAGE}
cluster: ${env:PRISMA_CLUSTER}
disableAuth: ${env:PRISMA_DISABLE_AUTH}
secret: ${env:PRISMA_SECRET}

[marktani]

This does look like a bug when using environments variables for disableAuth, thanks @johnslemmer! I also agree that there is an overlap of disableAuth and secret, that could be combined into a single mechanism.

[lrholmes]

Any progress on this issue? Would be nice to be able to control disableAuth with env vars.

[marktani]

disableAuth has been removed from prisma.yml in version 1.7.

If you don't want to authenticate your Prisma service, remove the secret property.

[johnslemmer]

Thanks @marktani !