Prisma

Prisma wants a `PRISMA_CONFIG` env var with line breaks in it.. but I have my prisma server deployed on Amazon ECS which does NOT like supporting line breaks in env vars... is there an alternate way to provide this info?

<@U0RQY0KK5> is there an alternate way to provide a prisma server with port, managementApiSecret, and database info other than using a multiline environment variable (yaml in env, it seems??)

because I can no longer just put `\n` in my ecs task definition json, it gets escaped now, so my server is just sitting there broken.

We’re deploying some of our Prisma servers on ECS as well, using the config env var without issues. We do that programmatically. Are you doing the deployment by hand?

<@U785TRF34> this is our first foray into it so we were using the aws console by hand, yeah; it appears the angular form they use for tweaking task info was the cause of my troubles. I was able to use the aws cli to send the json over with the line breaks and all seems well in the world now. Thanks!