How to escape multiline values in .env file

First of all, thanks a million for this action, it’s super useful.

I was wondering how to escape multiline env vars. let’s say I have a cert that I want to pass to my .env file from a github secret. This works locally because I can wrap the cert in quotes in my local .env file. How can I accomplish the same thing with this action? I don’t think it does this by default, because right now I’m getting the following error when I try to run docker-compose

Run docker compose -f docker-compose.yml -f production.yml build
unexpected character "+" in variable name near "***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\n***\nPOSTGRES_DB=***\nPOSTGRES_HOST=***\nPOSTGRES_PASSWORD=***\nPOSTGRES_PORT=***\nPOSTGRES_USER=***\nREDIS_HOST=***\nREDIS_PASSWORD=***\nREDIS_PORT=***\n"
Error: Process completed with exit code 1.

[justintemps]

I’m specifically thinking of an RSA key or some similar value where the line breaks are meaningful and have to be encoded in some way.

In my instance, I was using dotenv in a Node.js project which supports wrapping multiline variables in quotes like this.

PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
...
HkVN9...
...
-----END DSA PRIVATE KEY-----"

I guess in this situation, create-envfile needs to know if you’re intentionally passing in a variable that has linebreaks or if you’re not and it should through an error.

This seems a little hacky, but may be just adding something to the prefix like:

envkey_multiline_SECRET_KEY

[justintemps]

Yea @AngelOnFira that would be awesome.