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
Create a function for Operator (somewhat similar to presign_read) which generates a permanent publicly accessible URL to the resource. For example, I'm using Google Cloud Storage emulator and I have configured Gcs service like this:
Many object storage services such as Google Cloud Storage and S3 allow public read access to files. Operator nicely abstracts all these services, but since it doesn't have the ability to generate permanent and publicly accessible links, I loose this abstraction.
Additional Context
As an alternative, I tried to use .info() to find the necessary information to generate the url. However, neither Operator nor OperatorInfo expose endpoint, which further complicates workarounds.
Are you willing to contribute to the development of this feature?
Yes, I am willing to contribute to the development of this feature.
The text was updated successfully, but these errors were encountered:
Feature Description
Create a function for
Operator
(somewhat similar topresign_read
) which generates a permanent publicly accessible URL to the resource. For example, I'm using Google Cloud Storage emulator and I have configuredGcs
service like this:Now let's say I want to access a file "myfile.txt". I would like to generate a direct public access URL that looks like this:
http://localhost:9199/v0/b/test/o/myfile.txt?alt=media
Problem and Solution
Many object storage services such as Google Cloud Storage and S3 allow public read access to files.
Operator
nicely abstracts all these services, but since it doesn't have the ability to generate permanent and publicly accessible links, I loose this abstraction.Additional Context
As an alternative, I tried to use
.info()
to find the necessary information to generate the url. However, neitherOperator
norOperatorInfo
exposeendpoint
, which further complicates workarounds.Are you willing to contribute to the development of this feature?
The text was updated successfully, but these errors were encountered: