I'm having a tough time moving from 1.6 to 1.8. In particular,

# prisma.yml
# ...
hooks:
  post-deploy:
    - echo "Deployment finished"
    - graphql get-schema --project prisma
    - graphql prepare

with

#. .graphqlconfig.yml
#... 
  prisma:
    schemaPath: src/generated/prisma.graphql
    extensions:
      prisma: database/prisma.yml
      prepare-binding:
        output: src/generated/prisma.ts
        generator: prisma-ts

does not generate a new schema at src/generated/prisma.graphql on

prisma deploy

. What am I missing?

Did you add the post deployment hooks to

prisma.yml

?

I did. I was confused because if the

deploy

diff doesn't see a change, the deployment hook will not generate a new

prisma.graphql

even though it acts like it is. Is it possible to change that behavior so it also says "no changes detected?"

Oh sorry you shared the hooks already, didn't see that! 🙂 What do you mean with "it is acting like it is"? What happens when you run the command from the CLI directly?

yup - what happens when you run

graphql get-schema --project prisma

directly?

Same thing. My situation is probably an edge case. The exact flow was: 1. Do not commit

prisma.graphql

(we can debate if that's a good choice.. probably not) 2. Change an enum 3.

prisma deploy

4. Commit, push, and go home 5. New computer (at home),

prisma deploy

6. No change to

prisma.graphql

So on the home computer, I couldn't get an updated generated file until I changed the schema and

prisma deploy

this looks like a bug with

graphql prepare

, can you raise an issue here: https://github.com/graphql-cli/graphql-cli/issues?

Yeah that'd work!

yea that should probably be changed

For anyone looking in, here's the issue. https://github.com/graphql-cli/graphql-cli/issues/297

thanks a lot 🙌