Bug report for google-cloud-storage-deploy pipe

[Andrey Bronin]

I'm using google-cloud-storage-deploy pipe v. 0.3.1

pipe: atlassian/google-cloud-storage-deploy:0.3.1

Steps to reproduce is very simple. I'm using it exactly like this documentation sample

script:
  - pipe: atlassian/google-cloud-storage-deploy:0.3.1
    variables:
      KEY_FILE: $KEY_FILE
      PROJECT: "my-project"
      BUCKET: "my-bucket"
      SOURCE: "."

 $KEY_FILE is a string with double quotes and everything else you got from Google Cloud. Like this:   {"a":"b", "c":d"}.

This key (actually even exactly this pipeline variable $KEY_FILE) used in other scripts to log into the Google Cloud Container Registry (you need the key with full read-write permissions to Google Cloud Storage to push containers there, then key is 100% good and working good).

Then i immediately go this error

ERROR: (gcloud.auth.activate-service-account) Could not read json file /tmp/key-file.json: No JSON object could be decoded

[davina · Accepted solution]

Hi @Andrey_Bronin

You need to base64 encode the contents of KEY_FILE and save it as a pipelines variable.

Let me know if this helps,

Davina

[Andrey Bronin]

This helps. Thank you.

[Md Parvez Alam]

Could you please help me here

https://community.atlassian.com/t5/Bitbucket-Pipelines-questions/Issue-with-source-in-pipeline-cloud-storage/qaq-p/1556141