hey all im trying to setup prisma server using docker stack, and i want to use secrets for the configuration. It's not clear if/how I can do that, the configuration yaml seems to be passed as an environment variable. Is there a way I can have it use a file instead?

Can you please point out to the docs you are referring to? Are you referring to Prisma.yml to have configuration via file?

You want to set docker variables via file? When setting up Prisma?

that's how Docker propagates secrets, it creates files in

/run/secrets/

so putting them in environment variables is tricky

I am not clear on which environment variable you want to set yet.. can you please elaborate by an example? 🙂 Generally, both

prisma.yml

and

docker-compose.yml

files support .env files https://docs.docker.com/compose/env-file/

I'm trying to set

PRISMA_CONFIG

from a secrets file.

Yes, then you should be able to use the .env file as per the

docker-compose.yml

documentation! => https://docs.docker.com/compose/env-file/#syntax-rules

i do not believe this solves the problem, this is effectively the same as declaring the env variables in the compose.yml file. The secrets are inside the container, mounted by the docker process.

Aha! Got it. You want to not have the secrets in container at all. There are ways to do that, will get back with some resources!

no no, the secrets are in the container (mounted by the docker process)...but they are files, so i want to be able to load the config from a file somehow. For example with postgres you can do

POSTGRES_USER_FILE: /run/secrets/postgres_user

as an environment variable in the docker-compose.yml and it will slurp the contents of the file and use that as the POSTGRES_USER env variable.

Aha! got it.. I am afraid this is not supported yet, can you please create a feature request for this? Thanks!

hm, i think you guys may actually support it already. I just found this while digging through the code; PRISMA_CONFIG_PATH

Interesting, can you please point me out to a resolution? I will persist that for future queries.

here: https://github.com/prismagraphql/prisma/blob/665eb16138dfea9082746e21743121eccfc41419/server/libs/prisma-config/src/main/scala/com/prisma/config/ConfigLoader.scala#L48 it looks like it attempts to read from PRISMA_CONFIG, and if that fails it checks here: https://github.com/prismagraphql/prisma/blob/665eb16138dfea9082746e21743121eccfc41419/server/libs/prisma-config/src/main/scala/com/prisma/config/ConfigLoader.scala#L21 to find the config file location

Thanks for the details! I will get back to you on this after communicating internally! 👍