When I use creds: ${{ secrets.GOOGLE_APPLICATION_CREDENTIALS_DEV_2 }} I get error

[aseem-heg]

Does the secret variable name have to be GOOGLE_APPLICATION_CREDENTIALS or can it be different?
When I use a different secret name I get error - invalid json file "/tmp/gce-cloudsql-proxy/key.json": unexpected end of JSON input

[panjek26]

same with me

[MaximusMcCann]

Same

[ayy-em]

exit code 124

same json parsing trouble, I guess here, is there a solution?

[eboraks]

Same problem :(

[brettski]

This is strange. I don't see any name requirements in the YAML file, and I wonder if it's some Actions inputs limitation. If you shorten the name to something different, e.g., GOOGLE_APP_CREDS_DEV_2, does that work? (I don't currently have a project to test in.)

Its usage is really straightforward:

gce-cloudsql-proxy-action/action.yml

Line 32 in 145471a

echo '${{ inputs.creds }}' > /tmp/gce-cloudsql-proxy/key.json

Then read:

gce-cloudsql-proxy-action/action.yml

Line 39 in 145471a

-credential_file /tmp/gce-cloudsql-proxy/key.json \

[kbrashem]

I know for me, I ran into the invalid JSON file error because I was pointing to my credential path, not passing the actual credentials in.

Changing:

     - name: Start Cloud SQL Proxy
        uses: mattes/gce-cloudsql-proxy-action@v1
        with:
          creds: ${{ env.GOOGLE_APPLICATION_CREDENTIALS }}
          instance: ${{ env.DB_CONN_STR }}

to

      - name: Start Cloud SQL Proxy
        uses: mattes/gce-cloudsql-proxy-action@v1
        with:
          creds: ${{ secrets.GOOGLE_CREDENTIALS }}
          instance: ${{ env.DB_CONN_STR }}

fixed it form me. Hope this helps someone else.