Hello, I have a use case wherein I’d like to use Prisma deploy to setup my tables, but have all table migrations from then onward handled by a database versioning tool such as Liquibase or FlywayDB. However, I would also still like to be able to deploy my updated graphql schemas to the Prisma service using prisma deploy. I believe I can do this by setting

migrations: false

in the docker-compose.yml, and I thought this issue had gone away (with the help of @sorenbs) but I was wrong and get a series of errors upon doing that and running prisma deploy which do not appear when running prisma deploy without that setting on:

Errors:

  ExampleSetting1
    ✖ The required field `id` is missing and has to have the format: id: ID! @unique or id: UUID! @unique or id: Int! @unique.

 ExampleSetting2
    ✖ The required field `id` is missing and has to have the format: id: ID! @unique or id: UUID! @unique or id: Int! @unique.

  ExampleType1
    ✖ The scalar field `exampleField` has the wrong format: `[String!]` Possible Formats: `String`, `String!`

  ExampleType2
    ✖ The scalar field `exampleField` has the wrong format: `[String!]!` Possible Formats: `String`, `String!`

  ExampleType3
    ✖ The scalar field `exampleField1` has the wrong format: `[String!]` Possible Formats: `String`, `String!`
    ✖ The scalar field `exampleField2` has the wrong format: `[String!]` Possible Formats: `String`, `String!`

Deployment canceled. Please fix the above errors to continue deploying.

I was wondering why these errors show up only during a deployment with

migrations:false

, or perhaps if I can even do an initial deployment of my tables with a prisma service when I have that setting.

I have the same issue as @Bruno Prela

I have moved this to github https://github.com/prisma/prisma/issues/3095