Assigned
Status Update
Comments
cm...@google.com <cm...@google.com> #2
Please note that feature requests do not have any ETAs associated to them nor any guarantee that they will be implemented. Any further updates about this feature request will happen here.
tr...@gmail.com <tr...@gmail.com> #3
There are a number of ways this can be accomplished. I wrote a simple Cloud Function in Node that uses the npm Sharp library. Images are stored in a Cloud Storage bucket and resized on the fly. Cache control is used to limit resource usage. Unless the original images are particularly large, this seems to work reasonably quickly (100-200ms for a non-cached request). Performance could be further improved by saving resized images in Cloud Storage bucket.
I previously developed a image service on AWS where requests went directly to the S3 bucket. If no image was found, the request would be redirected to a Lambda function, which would generate the image, save it to S3, and return it to the browser. Sadly, GCP Cloud Storage buckets don't have a mechanism for server-side redirects when a 404 error is encountered.
I previously developed a image service on AWS where requests went directly to the S3 bucket. If no image was found, the request would be redirected to a Lambda function, which would generate the image, save it to S3, and return it to the browser. Sadly, GCP Cloud Storage buckets don't have a mechanism for server-side redirects when a 404 error is encountered.
mj...@gmail.com <mj...@gmail.com> #4
I think it's really important that Google takes action here. This is a standard feature on competitor CDN platforms like Vercel.
al...@google.com <al...@google.com>
is...@google.com <is...@google.com>
lu...@corbeilledor.com <lu...@corbeilledor.com> #5
this is pretty crucial
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #6
Hello,
Thanks for reporting the issue. This has been forwarded to the Engineering Team so that they may evaluate it. Please note that there are no ETAs for this issue. All communication regarding this issue is to be done here.
va...@google.com <va...@google.com>
su...@google.com <su...@google.com>
fr...@gmail.com <fr...@gmail.com> #7
Feel like I'm witnessing a game of hot potato played out in extremely slow motion.
me...@gmail.com <me...@gmail.com> #8
Being waiting for this for years.
lo...@gmail.com <lo...@gmail.com> #9
same here, come on google
ro...@carohq.com <ro...@carohq.com> #10
I'm curious if this is the right place to get this prioritized. Would we have better luck pushing for resourcing if we asked on one one of the cloud forums and got more user votes? Would really love to see this feature as opposed to using something external :)
ru...@simplify.jobs <ru...@simplify.jobs> #11
This is kinda embarrassing since almost every other cloud provider, big and small have this feature
Description
The request could be either implementing an Image Service as part of GCP products or to add these functionalities to the current Google Cloud Storage client library.
[1]
[2]