Google-Cloud-Storage | Setup Google Cloud Storage to upload and download | Cloud Storage library

As @dko512 mentioned in comments, issue was resolved by recreating and redeploying the Cloud Function.

Posting the answer as community wiki for the benefit of the community that might encounter this use case in the future.

Feel free to edit this answer for additional information.

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

You can use a new gcloud feature and impersonate your local credential like that:

After doing some more research online I realized that installation of some packages is missed due to some existing packages. This issue helped me realize I need to reorder the position of google-cloud-tasks in my requirements.txt. So what I did was pretty simple, created a new virtualenv installed google-cloud-tasks as my first package and then installed everything else and finally the problem is solved.

Long story short the issue is the order in which packages are installed and that's why some packages are getting missed.

Implicit relative imports are not anymore supported as documented:

There is no longer any implicit import machinery

So if Google.py is in the same directory as the code you pasted, you have to reference it's realtive location explicitly.

If the problem is that the file can not be located in CloudHub try instead this method to reference it as described in this KB article:

Ok I misunderstood you at the beginning.

When you are creating GKE cluster you can specify which GCP Service Account will be used by this cluster, like below:

By Default it's Compute Engine default service account (71025XXXXXX-compute@developer.gserviceaccount.com) which is lack of a few Cloud Product permissions (like Cloud Storage, it has Read Only). It's even described in this message.

If you want to check which Service Account was set by default to VM, you could do this via

Compute Engine > VM Instances > Choose one of the VMs from this cluster > In details find API and identity management

So You have like 3 options to solve this issue:

1. During Cluster creation

In Node Pools > Security, you have Access scopes where you can add some additional permissions.

• Allow full access to all Cloud APIs to allow access for all listed Cloud APIs
• Set access for each API

In your case you could just use Set access for each API and change Storage to Full.

2. Set permissions with a Service Account You would need to create a new Service Account and provide proper permissions for Compute Engine and Storage. More details about how to create SA you can find in Creating and managing service accounts.

3. Use Workload Identity

Workload Identity on your Google Kubernetes Engine (GKE) clusters. Workload Identity allows workloads in your GKE clusters to impersonate Identity and Access Management (IAM) service accounts to access Google Cloud services.

For more details you should check Using Workload Identity.

Useful links

• Configuring Velero - Velero is software for backup and restore, however steps 2 and 3 are mentioned there. You would just need to adjust commands/permissions to your scenario.
• Authenticating to Google Cloud with service accounts

In the thread you linked, there are several solutions, and an interesting one seems to be that a package named fitz conflicts with PyMuPDF, as they both use the same top name inside a script (being fitz). I see both libraries are in your requirements.txt, so this could be the cause of this error. I tested adding both libraries inside a Cloud Function and received the same error, which was resolved after removing fitz 0.0.1.dev2 from the file, and using only PyMuPDF.

You can see another example of this behavior from this GitHub issue.

Using mvn dependency:tree you can discover there's a mix of grpc-java 1.41.0 and 1.42.1 versions in your dependency tree. google-cloud-datastore:2.2.0 brings in grpc-api:1.42.1 but the other dependencies bring in grpc version 1.40.1.

grpc-java recommends always using requireUpperBoundDeps from maven-enforcer to catch Maven silently downgrading dependencies.