since when is endpoint deprecated? the 1.7/1.8 upg...
# orm-helpv
veksen
06/14/2018, 5:36 PMsince when is endpoint deprecated? the 1.7/1.8 upgrade guide doesn’t reference this.
Copy code
endpoint: ${env:PRISMA_ENDPOINT}
secret: ${env:PRISMA_MANAGEMENT_API_SECRET}
datamodel: datamodel.graphql
hooks:
post-deploy:
- graphql get-schema --project prisma
- graphql preparen
nilan
06/14/2018, 5:43 PMit's not deprecated. Somewhere in your dep tree there is an old version of graphql-config-extension-prisma flying around.
nilan
06/14/2018, 5:44 PMnpm list graphql-config-extension-prisma and npm list graphql-config-extension-prisma -g will help you find the cause
v
veksen
06/14/2018, 5:46 PMright: graphql-config-extension-prisma seem to be coming from graphql-cli
veksen
06/14/2018, 5:47 PMfrom yarn.lock:
n
nilan
06/14/2018, 5:47 PMYes, that's good.It's just an old version which is the problem.
nilan
06/14/2018, 5:48 PMA version that doesn't know the endpoint property.
v
veksen
06/14/2018, 5:49 PM Copy code
graphql-cli@2.16.3:
version "2.16.3"
resolved "<https://registry.yarnpkg.com/graphql-cli/-/graphql-cli-2.16.3.tgz#3042b7dbcdca33fe4108862de64bd42834ff5bec>"
dependencies:
...
graphql-config-extension-prisma "0.0.11"veksen
06/14/2018, 5:49 PMlatest version
n
nilan
06/14/2018, 5:51 PMDid you check it globally as well?
v
veksen
06/14/2018, 5:52 PMahhhhhh… my global version is still 1.6
veksen
06/14/2018, 5:53 PMwith global @ 1.9, back to
Cluster secret in env var PRISMA_MANAGEMENT_API_SECRET does not match for cluster localn
nilan
06/14/2018, 5:54 PMwhere does your Prisma server live? is it locally in docker?
nilan
06/14/2018, 5:54 PMwhat's its version?
v
veksen
06/14/2018, 5:54 PMlocally yes
n
nilan
06/14/2018, 5:54 PMdocker ps
v
veksen
06/14/2018, 5:54 PMit’s still 1.6
veksen
06/14/2018, 5:54 PMbut I don’t care to scrap it
veksen
06/14/2018, 5:55 PMI guess I can just destroy it and it will build a new one?
n
nilan
06/14/2018, 5:55 PMWell that's probably the cause for the error message
nilan
06/14/2018, 5:55 PMYou can also do docker pull
v
veksen
06/14/2018, 5:57 PMit works! thank you so much
fast parrot 1
veksen
06/14/2018, 5:59 PMon the task of deployment this week, hopefully docker-compose.yml will make things easier :]
💯 1
l
lawjolla
06/14/2018, 10:06 PM@veksen what did you do? I'm stuck in the 1.6 -> 1.9 too
v
veksen
06/14/2018, 10:25 PM@lawjolla do you have live data?
veksen
06/14/2018, 10:27 PMin my case I’m still in dev, so I destroyed the prisma local Docker container, and deployed a new one
l
lawjolla
06/14/2018, 10:31 PMI do. I’m considering doing the same though and reimporting the data
lawjolla
06/14/2018, 10:32 PMIt’s in production on digital ocean
v
veksen
06/14/2018, 10:36 PMtagged you here with what I did to upgrade
veksen
06/14/2018, 10:38 PMplus left mini-guide/note to my co-worker (she was on a public cluster and moving to local Docker):
- Set up local Docker
- Upgrade local Prisma to 1.9 (npm i -g prisma or yarn add global prisma)
- Set up .env according to .env.example
- yarn prisma deploy
- yarn dev
- Should be good
l
lawjolla
06/18/2018, 4:35 PMI eventually gave up, exported the data, tore down the 1.6 cluster, upgraded Prisma, spun up the 1.9 cluster, and imported the data. It worked fine
v
veksen
06/18/2018, 6:45 PMyeah now I'm having trouble on my other computer..