You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running nixery on a GCP instance with the default service account / in a cloud run function / GKE, nixery should still be able to emit signed URLs to GCS buckets. It currently has code only doing this if GOOGLE_APPLICATION_CREDENTIALS is set explicitly.
The text was updated successfully, but these errors were encountered:
It should not do this without the feature being explicitly enabled, as the signBlob API unfortunately requires service account impersonation credentials. Useful to have though!
When running nixery on a GCP instance with the default service account / in a cloud run function / GKE, nixery should still be able to emit signed URLs to GCS buckets. It currently has code only doing this if GOOGLE_APPLICATION_CREDENTIALS is set explicitly.
The text was updated successfully, but these errors were encountered: