anyone know how to solve this issue: No cluster se...
# orm-helpi
immediato
02/21/2019, 2:36 PManyone know how to solve this issue: No cluster set. Please set the “cluster” property in your prisma.yml. i’m seeing this error when i try to run: graphql get-schema -p prisma (more info in thread)
immediato
02/21/2019, 2:42 PMi’m having a lot of issues while trying to create both a dev and prod environment.
immediato
02/21/2019, 2:43 PManother issues i’m having is how you use an environment variable in the prisma.yml file
immediato
02/21/2019, 2:43 PMendpoint: ${env:PRISMA_ENDPOINT} isn’t working when i try to use prisma token
h
Harshit
02/21/2019, 2:47 PMHi,
Can you please paste the cluster error, also you can generate the graphql schema using the prisma cli only
for the second one make sure you have the .env file in the same directory or pass in the
-ei
immediato
02/21/2019, 2:48 PMHere’s the full text:
immediato
02/21/2019, 2:48 PMgraphql get-schema -p prisma
⠸ [ “[WARNING] in prisma/prisma.yml: A valid environment variable to satisfy the declaration ‘env:PRISMA_ENDPOINT’ could not be found.” ]
[ “[WARNING] in prisma/prisma.yml: A valid environment variable to satisfy the declaration ‘env:PRISMA_SECRET’ could not be found.” ]
✖️ No cluster set. Please set the “cluster” property in your prisma.yml
immediato
02/21/2019, 2:49 PMam i running the wrong command for the schema?
h
Harshit
02/21/2019, 2:49 PMok the main cause of the error here is the fact that you are not correctly passing in the environment variable
Harshit
02/21/2019, 2:49 PMI think you can generate the schema by using prisma cli only
Harshit
02/21/2019, 2:50 PMcan you tell the cli version you are using(prisma -v) ?
i
immediato
02/21/2019, 2:50 PM1.26.3
h
Harshit
02/21/2019, 2:50 PMok, then add this to the prisma.yml file
Harshit
02/21/2019, 2:51 PM Copy code
generate:
- generator: graphql-schema
output: ./generate/prisma-schemaHarshit
02/21/2019, 2:51 PMyou can change the output path
Harshit
02/21/2019, 2:51 PMand then run
prisma generatei
immediato
02/21/2019, 2:54 PMawesome
immediato
02/21/2019, 2:54 PMthat seems to have fixed that issue when i run that command with the -e flag pointing to the dev.env
2 Views