Switch environment file with `-e` flag

prisma2 -e .env-file

Use case, developing locally, deploying to lambda using serverless, my package.json would have the following script:

"deploy-production": "yarn prisma2 lift up --auto-approve && sls deploy --stage production",

To make it work without this, I need to do the following for all env vars

"deploy-production": "DB_URL=$(cat .env.production | grep DB_URL | cut -d '=' -f 2) yarn prisma2 lift up --auto-approve && sls deploy --stage production",

[schickling]

I like the idea but would suggest to call the argument --env-file same as Docker:

[dkozma]

This also seems relevant for making yarn prisma2 generate work with an .env in the project root (instead of the prisma folder) as discussed in #1519, unless someone else knows another way to run that without copying/symlinking my application’s .env file to the prisma folder (or managing multiple .env files).