How to upgrade prisma server deployed on fargate: ...
# orm-help
g
How to upgrade prisma server deployed on fargate: I have
managementApiSecret: ${PRISMA_MANAGEMENT_API_SECRET}
in
docker-compose.yml
(have deployed prisma in docker on AWS using prisma deploy on fargate tutorial and connected to RDS) Question: I need to upgrade server to
1.32
. How to do something like
docker-compose ... -e .env
? (I was reading comments which suggest that
prisma deploy -e .env
takes care of this; that's why I didn't noticed this when deploying) Docs:
docker-compose pull -e.env
won't work similarly. [https://www.prisma.io/docs/prisma-server/deployment-environments/docker-rty1/]
h
You can do it from AWS console
g
Hello @Harshit I am going to follow this doc and will report if anything messes up. But I was actually working on @divyendu's github suggestion from here, and it might not be fixed by upgrading server: https://github.com/prisma/prisma/issues/4424
EDIT: I upgraded server to 1.32.0 (CLI is at 1.32.2) by editing fargate.yml from cloudfront. Same error as reported on that github thread is faced again.
h
Please update the issue with the information. I think it's a confirmed bug that we need to fix