for anyone struggling with 1.7 - don't trust the upgrade guide, it's still necessary to specify

cluster

in the

prisma.yml

, otherwise an incorrect value is read from

~/.prisma/config.yml

and weird things happen https://github.com/graphcool/prisma/issues/2305

Thanks for reporting @Daniel K.! I answered in the github issue 🙂

would be useful to see some changelog ... what's the actual fix, removal of cluster, or the need for config.yml ?

It will go into the changelog soon, but we first keep it in the beta channel until it's confirmed. The fix is, that the env var is correctly read and your non local cluster url is still handled as a local cluster

well, I am failing to understand why the config.yml is still needed since you have full endpoint url (and secret provided with env var) ... in my opinion it's major confusion there since "prisma cluster" command is deprecated and yet the config managed by that command is still used and necessary

@Daniel K. the config is not necessary. That was just a bug. The concept of a cluster "name" doesn't matter anymore. Did you try the

prisma@beta

? It's now released under

prisma@1.7.4