[FEATURE] Adding TTL to kv-cache

[minibox24]

Is your feature request related to a problem?

.

Describe the solution you'd like

Add a TTL to the kv-cache to ensure that unneeded keys are automatically deleted.

Describe alternatives you've considered

.

@opennextjs/cloudflare version

0.5.10

Additional context

I realize that the current version is risky for production, but having a KV TTL would be a big help.

Before submitting

• I have checked that there isn't already a similar feature request
• This is a single feature (not multiple features in one request)

[james-elicx]

To provide a little context, the reason that the KV cache does not currently use a TTL is because it falls back to using the build-time cache assets if there is no KV entry. As a result, it would serve rather old, stale responses if we didn't keep a KV entry for a cache entry after a revalidation happens.

The best way to deal with this would probably be for us to upload the build-time cache assets to KV when your app is deployed, instead of us relying on serving them separately from Workers Static Assets like we currently do.

We've started looking at what populating a binding at build/deploy-time might look like (#436 has a POC), so once we decide on how we want to proceed with populating bindings, we should be able to change the KV cache to use it and have proper support for KV TTLs.