I haven't found a way to perform the same function which we had pre-1.7, that's one of the main features I really liked.
npm i -g graphql-cli
hooks:
post-deploy:
- echo "Deployment finished"
- graphql get-schema --project database
- graphql prepare
prisma deploy
This is example .graphqlconfig.yml:
projects:
app:
schemaPath: src/schema.graphql
extensions:
endpoints:
default: http://localhost:5000/graphql
database:
schemaPath: src/generated/prisma.graphql
extensions:
prisma: prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
Also covered in the upgrade guide.
Did that, still doesn't want to do it, I'll show mine if you want and it keeps saying
Syntax Error: Unexpected Name "F"
projects:
main_hub_app:
schemaPath: src/schema.graphql
extensions:
endpoints:
default: "http://localhost:4000"
prisma:
schemaPath: src/generated/prisma.graphql
extensions:
prisma: prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
endpoint: http://localhost:4466
datamodel: database/datamodel.graphql
hooks:
post-deploy:
# - echo "Deployment finished"
- graphql get-schema --project prisma
- graphql prepare
I found out the problem it seems the previous generated code was causing an error, once I removed them, it built new ones, but I doubt that's intended, but it seems you need to delete the old one first.
Docs seem to be strangely incomplete. There is a mention of these hooks in upgrade guide, but in actual structure doc there is not a word about it 😕
It is very difficult for me with a working project because of this
$ cat .graphqlconfig.yml
projects:
app:
schemaPath: src/schema.graphql
extensions:
endpoints:
default: http://localhost:4000
prisma:
schemaPath: src/generated/prisma.graphql
extensions:
prisma: database/prisma.yml
prepare-binding:
output: src/generated/prisma.ts
generator: prisma-ts
```bash
$ cat database/prisma.yml
endpoint: ${env:PRISMA_ENDPOINT}
datamodel: datamodel.graphql
secret: ${env:PRISMA_SECRET}
hooks:
post-deploy:
- graphql get-schema --project prisma
- graphql prepare
**Error**
```bash
$ prisma deploy
Deploying service `autoparts` to stage `dev` to server `default` 426ms
Service is already up to date.
post-deploy:
Running graphql get-schema --project prisma !
! "graphql" �� ���� ����à¥ï¿½ï¿½ï¿½ ��� ���è¥ï¿½
! ��������, �ᯮ��塞�� ï¿½à®£à ¬ï¿½ï¿½ï¿½ ��� ������ ä ©ï¿½ï¿½ï¿½.
!
Get in touch if you need help: https://www.graph.cool/forum
To get more detailed output, run $ export DEBUG="*"
how do i generate files ?
Hello Everyone,
I am having the same issue, but I get a different Error Output.
Below is my prisma.yml:
```secret: ${env:PRISMA_SECRET}
datamodel: datamodel.graphql
seed:
import: seed.graphql
endpoint: https://example-rds-aws_example.prisma.sh/example/example-project/dev
hooks:
post-deploy:
- echo "Deployment finished"
- graphql get-schema --project prisma
- graphql prepare
Below is my graphqlconfig.yml:
```projects:
app:
schemaPath: "src/schema.graphql"
extensions:
endpoints:
default: "http://localhost:4000"
prisma:
schemaPath: generated/prisma.graphql
extensions:
prisma: prisma.yml
perpare-binding:
output: generated/prisma.ts
generator: prisma-ts
Below is the Error I receive:

1) Why does CLI respond saying Invalide prisma.yml file?
2) After the v1.7.1 upgrade, I am not able to deploy because of the endpoint in prisma.yml
Is there something I'm doing incorrectly?
@FredyC: thanks for your feedback, we added docs here. Please create a new issue if you feel something in the documentation could be improved 🙂
@overpod: syntactically, everything looks good to me. However, the error message could hint towards an encoding issue. Could you please create a new bug report, including a minimal setup for reproduction here?
@yoorw: One part of your issue is being discussed here: https://www.graph.cool/forum/t/how-to-fix-invalid-prisma-yml-file-prisma-yml-should-not-have-additional-properties-additionalproperty-endpoint-errors/3303/2?u=nilan. And then, it looks like you are not setting the env variable PRISMA_SECRET, but you use it in your prisma.yml file.
I am closing this issue, as the original question is answered.
Please don't reply here, but create a new issue if you have further questions for your indivual problems.
Most helpful comment
This is example .graphqlconfig.yml: