1.7 is hell of the update ... I can understand the...
# orm-helpd
Daniel K.
04/28/2018, 7:48 PM1.7 is hell of the update ... I can understand they are trying to give us more control, but things are suddenly so complicated and even broken in some cases ... I do love Prisma, but I think there should be a slower pace for changing stuff so drastically 😕
n
nilan
04/28/2018, 7:51 PMCan you share the biggest pain points you are going through? I'd love to help you out with that 🙌
I also want to share that you can operate your own Prisma server on any version you want 🙂
f
Fi1osof
04/28/2018, 7:56 PM@Daniel K. agree
d
Daniel K.
04/28/2018, 7:56 PMfor starters the upgrade guide is rather lacking, mostly talking about changes and how nice it works with new projects, but older projects are left wondering how to really upgrade those regarding docker and tokens
f
Fi1osof
04/28/2018, 7:57 PM@nilan just example prisma init fullstack react, like it was on 1.0.2-1.6.3
d
Daniel K.
04/28/2018, 7:58 PMalso I don't like deprecating "local" command, it was so easy with those, I really did not want to dive into Docker documentation
👍 2
Daniel K.
04/28/2018, 8:09 PMoh and "Simpler Prisma server authentication" feels quite opposite, instead of a single secret, there is now management api secret ... it's rather hard to figure what is used for which operation
Daniel K.
04/28/2018, 8:20 PManother point of confusion is that cluster are supposed to be called servers, but there is still the .prisma/config.yml with clusters
Daniel K.
04/28/2018, 8:23 PMfor example, I have recreated containers on my AWS and it's yelling at me about invalid authentication token ... it's unreal to figure out what's wrong and where
Daniel K.
04/28/2018, 8:25 PM@nilan btw, regarding your comment about operating any version I want ... if I want to get bugfixes (eg. for subscriptions) I kinda don't have this choice 😕
n
nilan
04/28/2018, 8:26 PMOf course, I just mentioned that to say that you can do so in your own time 🙂
nilan
04/28/2018, 8:27 PMThanks a lot for your feedback, I'll go through it soon 🙌
d
Daniel K.
04/28/2018, 8:41 PMhttps://github.com/graphcool/prisma/issues/2273#issuecomment-385203974
and this is probably the biggest pain point in the end
b
bazaglia
04/28/2018, 10:02 PMI liked the 1.7 upgrade. Having control to my docker prisma application and database is nice. I also liked the authentication: a management api and a per service key is so flexible and fits exactly to my use case. But I do agree that
prisma local👍 1
d
Daniel K.
04/29/2018, 6:44 AMmore gradual updates would be better, ideally adhere to semver and keep breaking changes for major version while supplying bugfixes and additions
p
peter
04/29/2018, 8:15 PMman I am feeling these pain points right now
peter
04/29/2018, 8:16 PMvery unhappy with the 'migration guide', so far NOTHING is working as described
n
nilan
04/30/2018, 3:18 PMinstead of a single secret, there is now management api secret@Daniel K. Previously, there was a key pair for Prisma server authentication. Now, only one secret is required (symmetric JWT encryption). From two secrets to one, not from one to one 🙂
also I don't like deprecating "local" command, it was so easy with those, I really did not want to dive into Docker documentationcheck https://github.com/graphcool/prisma/issues/2312 🙂 plus, thanks for your activity on Github as well 👌
d
Daniel K.
04/30/2018, 3:28 PMthat "pair" you are talking about haven't really bothered me, because I never got to the point to care about that as it required some docker tweaking
so I don't see much of a difference now except I cannot avoid docker now 🤡