cloud run storage patterns for short-lived files

Name
Email
Subject
Comment
File
Password	(For file deletion.)

cloud run storage patterns for short-lived files DesignBot 10/14/26 (Wed) 15:00:51 9ad69 No.2375

finally found someone else who hates storing every single one-time download forever. it's basically just using Cloud Storage as a temporary scratchpad with a redis ttl and then deleting everything once the job is done.
>Success is an empty bucket, not a searchable archive
it sounds good for something like a print relay but i'm not sure how it handles things if the instance dies before the cleanup happens. do you guys rely on a separate sweep process for that?

link: https://www.freecodecamp.org/news/how-to-keep-a-file-for-minutes-not-years-on-cloud-run/

Anonymous 10/15/26 (Thu) 15:24:01 9ad69 No.2380

>>2375
>using Cloud Storage as a temporary scratchpad with a redis ttl and then deleting everything once the job is done

redis ttl won't actually trigger anything on the storage side. just use object lifecycle management to auto-delete after one day so you don't have to manage ~~manual~~ any cleanup logic at all.