Unable to prisma deploy

[adetoola]

I have prisma installed globally. Running prisma -v returns prisma/1.23.1 (windows-x64) node-v11.1.0 This same issue has resurfaced in the latest version of prisma@1.23.1

However, I when I ran prisma deploy I get the following error:

 !    Your `cluster` property in the prisma.yml is missing the workspace slug.
 !    Make sure that your `cluster` property looks like this: <workspace>/<cluster-name>. You can also remove
 !    the cluster property from the prisma.yml
 !    and execute prisma deploy again, to get that value auto-filled.

Get in touch if you need help: https://www.prisma.io/forum/
To get more detailed output, run $ export DEBUG="*"

Finally, if I downgrage to one of the earliest version of prisma like 1.10.2, I don't encounter any error.

This issue is related Unable to prisma deploy or yarn dev (prisma/playground) after 1.7.1 upgrade. Running on Prisma Cloud which is marked closed.

[billfienberg]

I was able to fix this on my machine by adding my slug into my endpoint path between the top level domain and service.

Once you're logged into the Prisma console, you can get your slug via:

1. The URL (https://app.prisma.io/**firstname-lastname-123abc**/services)
2. The Workspace Settings page i. Click the Settings link ii. Click the Workspace link

Format:

Old Format: https://${region}.prisma.sh/${service}/${stage} New Format: https://${region}.prisma.sh/${slug}/${service}/${stage}

For example:

Before: https://us1.prisma.sh/comedian/dev After: https://us1.prisma.sh/donald-glover/comedian/dev

Source:

Docs: https://www.prisma.io/docs/releases-and-maintenance/upgrade-prisma/upgrade-to-1.7-jgpt#example:-deploying-to-a-prisma-sandbox-in-the-cloud

[mvortizr]

Thank you @billfienberg i was having the same problem, i solved it by using your method but I couldn't see anything inside the Prisma console but a "Succesfully authenticathed" message. But the url was https://app.prisma.io/{MySlug}/services/onboarding/step-4 so I just changed prisma endpoint like you said https://us1.prisma.sh/{MySlug}/blablabla/dev and everything was solved. Thank you for sharing your solution.

[adetoola]

This issue have been resolved in the latest version of prisma-cli

[DanS]

This issue still reproduces for me on prisma@1.29.1

[jeremyeaton89]

same issue with prisma@1.30.1

[feynon]

The same issue persists for me on Prisma CLI version: prisma/1.34.10 (linux-x64) node-v13.7.0