Closed sww314 closed 3 years ago
Please ask this on Stack Overflow. I believe this is either an issue with how you pass creds to the container –or something wrong with Python client libraries. Cloud Run provides a token in the container runtime just fine, and the rest is handled by client libraries. Maybe consider opening an issue in the relevant code repo. https://cloud.google.com/python/docs/reference
Here is the stackoverflow question in case anyone stumbles on this.
There is no documentation - that I can find on how to do this in Cloud Run. The same work arounds listed in https://github.com/googleapis/google-auth-library-python/issues/50 fails in Cloud Run, but works on a Compute Instance.
I think because you can set the allowed scopes on VM instance.
https://stackoverflow.com/questions/64234214/how-to-generate-a-blob-signed-url-in-google-cloud-run
Running a python image using the standard Service Account, I get an error trying to sign GCS blobs. Is there a work around? The same service account works fine with the JSON file is mounted (when I run the container locally).