Prisma1: "Workspace dev does not exist" when deleting service from demo server

[marktani]

Bug Report

Current behavior

When being logged in and running prisma delete with a service that is deployed to the demo server, you receive this response:

ERROR: Workspace dev does not exist

{
  "data": {
    "generateClusterToken": null
  },
  "errors": [
    {
      "message": "Workspace dev does not exist",
      "locations": [
        {
          "line": 3,
          "column": 9
        }
      ],
      "path": [
        "generateClusterToken"
      ],
      "code": 222
    }
  ],
  "status": 200
}

Get in touch if you need help: https://www.graph.cool/forum
To get more detailed output, run $ set -x DEBUG "*"

Reproduction

Use this prisma.yml and run prisma delete while being logged in

endpoint: https://eu1.prisma.sh/public-starscowl-123/workspace-dev-not-found/dev
datamodel: datamodel.graphql

Expected behavior?

The service is deleted.

[nhuesmann]

Glad to see this submitted, I've been losing my mind trying to delete a demo service I deployed! I ran into this issue after starting a project using the node-graphql-server-advanced boilerplate.

[vsimko]

Same problem here.
As a workaround you can still delete the services through the "prisma console" online.

[divyenduz]

Unable to replicate this with prisma cli 1.9. Tried the following:-

1. Demo server with public- name.
2. Demo server with workspace under my username.
3. Node advanced boilerplate as suggested in a comment.

Please comment / reopen if this persists for you but do remember to update to 1.9+ via npm install -g prisma.

Thanks!