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
I am running fake-gcs-server in my local compose stack and connect to it via gcloud.aio.storage.Storage.
I set up the api_root via STORAGE_EMULATOR_HOST, and can see that the correct one is used.
However, when generating a signed URL for a blob, I receive one starting with storage.googleapis.com.
I am suspecting that is due to the hardcoded HOST referred above.
Is this usage intended? Or should the HOST be pointing to the api_root instead?
The text was updated successfully, but these errors were encountered:
gcloud-aio/storage/gcloud/aio/storage/blob.py
Line 34 in e738eb8
Hello,
I am running
fake-gcs-server
in my local compose stack and connect to it viagcloud.aio.storage.Storage
.I set up the
api_root
viaSTORAGE_EMULATOR_HOST
, and can see that the correct one is used.However, when generating a signed URL for a blob, I receive one starting with
storage.googleapis.com
.I am suspecting that is due to the hardcoded
HOST
referred above.Is this usage intended? Or should the
HOST
be pointing to theapi_root
instead?The text was updated successfully, but these errors were encountered: