Prisma1: Provided query doesn't include model name - newly deployed service

[jjaybrown]

Bug Report

*Current behaviour *

Deploying a new service with a subscription definition results in

  Subscription
    ✖ The provided query doesn't include any known model name. Please check for the latest subscriptions API.

Reproduction

service: serviceName
stage: dev
cluster: local
disableAuth: true
datamodel:
  - types.graphql
  - enums.graphql
subscriptions:
  fetchSnippetLexicons:
    query: subscriptions/fetch-snippet-data.graphql
    webhook: ${URL}

Removing the subscription and deploying the service, then introducing the subscription into the schema works.

If your problem can be reproduced with a certain service definition, please create a new GitHub repository with the reproduction instructions.

Expected behaviour?
A new service with a subscription should be deployed successfully.

[everdrone]

experiencing the same issue with v1.7.3

[marktani]

This still happens on 1.7.3. I'd love to see a a PR for this issue, let me know if you want to help 🙌

[danielrasmuson]

A work around to this issue is to...

1. remove the subscription section in your prisma.yml
2. prisma deploy
3. readd subscription section
4. prisma deploy

[everdrone]

@danielrasmuson yes, it works

but this bug makes the workflow "less automated", for example, if your prisma server is inside a docker container, you should write a shell script to first deploy without the subscription section, and then concatenating the subscriptions before deploying the second time.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[danielrasmuson]

I'm still experiencing this issue.

[donedgardo]

Having this same problem, @danielrasmuson workarounds works but the our automated deployments and CI tools are failing.
It looks like the subscription part of the build requires the deployment of the database.graphql model to be deployed first.

[mcmar]

Just experienced this too. The workaround is suitable for me, but definitely not intuitive. Seems that migrations should be run before attempting to validate the subscription listeners.

[mavilein]

Thanks for reporting this! 🙏 This is fixed in 1.15.3 which will be available in a few minutes.

[jjaybrown]

UPDATE: I hadn't updated the prisma server to 1.15 - confirmed working.

I'm still receiving this error, using prisma/1.15.3 (darwin-x64) node-v10.1.0