Determine best way to expire (e.g. delete) offline map packages, and add an option to extend the date

[rudokemper]

We don't want to have offline map packages, that are potentially large in size, sitting around forever -- at least, not without the user's input about wanting to extend their expiration date.

• Figure out an optimal expiration date (proposal to start: 1 year from creation).
• On the MapDashboard UI, add an option to extend the expiration date (e.g. by another year from when the user requests the extension).
• Once the expiration date is passed, we need to figure out a way to (1) delete the files and (2) update the db table row to set status = EXPIRED. (I think it will be good to keep a record of expired maps, for future reference - e.g. to use the same bounds and style for another map request.)

[rudokemper]

To discuss as an Awana Labs initiative with @luandro

[IamJeffG]

The idea I'm about to propose provides less control than you are what suggesting, but it's dead simple and you could do it today: Azure blob storage Lifecycle Management Policy

[rudokemper]

The idea I'm about to propose provides less control than you are what suggesting, but it's dead simple and you could do it today: Azure blob storage Lifecycle Management Policy

I think we'd still need a way to update the database to remove the offline map request record, though, right?

With this approach, we could have mapgl-tile-renderer check for files on a regular basis and update the DB to remove any that are missing.

[IamJeffG]

You could set both the blob expiration to 1yr and also -- but completely independently -- set the app to expire database records after 1yr (assuming the DB table already stores a "created-at" column). They don't necessarily need to rely on each other, just heavily document what you are doing.

DB record always exists before the blob, so in theory you should never have a "close race" where the blob is deleted minutes before the DB record and user gets an error if they try to download during that period. Or just set the blob expiry to 1 day longer than DB record.