I would like to suggest the use of CLOUD_PLATFORM scope instead of the DEVSTORAGE_FULL_CONTROL scope.
I am facing a problem with Jenkins deployed in GKE and using Workload identity as the authentication method for Jenkins agents where I cannot use this plugin because of the scope requirement.
The suggestion is also motivated by this lines:
"There are many access scopes available to choose from, but a best practice is to set the cloud-platform access scope, which is an OAuth scope for Google Cloud services, and then control the service account's access by granting it IAM roles."
I would like to suggest the use of CLOUD_PLATFORM scope instead of the DEVSTORAGE_FULL_CONTROL scope. I am facing a problem with Jenkins deployed in GKE and using Workload identity as the authentication method for Jenkins agents where I cannot use this plugin because of the scope requirement.
The suggestion is also motivated by this lines:
"There are many access scopes available to choose from, but a best practice is to set the cloud-platform access scope, which is an OAuth scope for Google Cloud services, and then control the service account's access by granting it IAM roles."
Found in Google documentation
This fixes #231
Testing done
I test the change manually and it seems to fix the problem described.