hey 👋 one of our Prisma deployments seems to be in a weird state. When I deploy a new field to a model, e.g.

fieldOne

, the CLI will show it being successfully added and

graphql get-schema --project database

running as a hook. However, the

prisma.graphql

file doesn't show the new field and the database isn't updated. If I add another field, e.g.

fieldTwo

, and deploy, then

fieldOne

is now added and the

prisma.graphql

shows it as a field. It's like the deploys are one step behind the changes to my data model. Has anyone seen anything similar?

I have not seen this before. Do you deploy directly to Prisma, or is it in a CI environment?

Hey 👋 we still see this quite often. We're deploying directly with the Prisma CLI. For example, I've just deployed and see these changes:

Changes:

  MyModel (Type)
  - Deleted field `field`

If I look at the generated

prisma.graphql

I'll see:

type MyModel implements Node {
  id: ID!
  field: String
}

What happens if you run

graphql get-schema --project database

in your CLI?

The

src/generated/prisma.graphql

stays the same

What is the entire output of the command?