Can't use multiple line val in env_vars

[onel]

TL;DR

I'm trying to deploy to cloud run and one of the env_vars has a value that is multi line, specifically it is a PEM key.
This seems to make the key not be used properly in cloud run UI.
The problem is with GH_APP_PRIVATE_KEY
Tried with with both "" and without.

In the google console UI the output looks like this

This might be a yaml question more than a deploy-cloudrun one.

Expected behavior

No response

Observed behavior

No response

Action YAML

- name: Deploy to Google Cloud Run
        uses: google-github-actions/deploy-cloudrun@v2

        with:
          service: ${{ env.RUN_SERVICE }}
          image: ${{ env.GAR_LOCATION }}
          region: ${{ env.REGION }}

          env_vars: |-
            DEBUG='False'
            GH_APP_PRIVATE_KEY=${{ secrets.GH_APP_PRIVATE_KEY }}

Log output

No response

Additional information

No response

[sethvargo]

Have you tried:

env_vars: |-
  GH_APP_PRIVATE_KEY="${{ secrets.GH_APP_PRIVATE_KEY }}"

If so, please provide the debug logs.

[onel]

Yes, I've tried with quotes as well.

This is the log output specifically for the deploy job (the link expires in 1 week)
https://pastebin.com/r75Qjzaq

[sethvargo]

Pasting the relevant bits here for history:

GH_APP_PRIVATE_KEY="***,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***=,***"= 

It looks like parsing is actually successful, but then re-serialization is incorrect.

[onel]

I see, so this might be a deploy-cloudrun bug?

[Azzerty23]

Is there a workaround for this?

[onel]

The workaround I went with is adding the PEM keys to the repo and loading them if dev / prod. Not ideal

[sethvargo]

There are a couple options:

1. Remove the newlines from the PEM:

   awk 'NF {sub(/\nr\r?/, ""); printf "%s\\n",$0;}'

2. Encode the PEM (e.g. base64) so it's safe to transport as a single line. Your application or workflow would need to decode it on the other side though.

3. Escape the newline on each row with a backslash (this is a fake private key we use in tests):

-----BEGIN PRIVATE KEY-----\
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDRJRbmz9Qi7or8\
G342x0t5eILuU/DmDz/K+aF+HCmKpiNMM3VVXop5r70jtuDwTg2Hj4Wq+/VUFy9m\
7N2c6NcjhekEZZbtGBoaiddffX7S54Y5La4ynJooLwkHm2mLp2et5gIjhwHiRvXa\
ftyRyC/83GkAjs88l5eGxNE=\
-----END PRIVATE KEY-----

[antoinedeschenes]

I imagine a good enhancement would be to support the same multiline syntax as GITHUB_ENV https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#multiline-strings