Downtime after `wrangler publish` about kv-asset-handler HOT 4 CLOSED

If you do this order (serially):

1. Write all assets out
2. Write out the new manifest

You should never see a 404.

I can imagine a couple ways to see a 404:

a. If you race the asset + manifest uploads then anyone seeing the new manifest might 404 on assets they aren't in KV yet.
b. If you do any deletes to clean up no-longer-existing pages, people who see a previous (cached) manifest might see 404s.

from kv-asset-handler.

we can probably leverage the listKeys feature: https://developers.cloudflare.com/workers/reference/storage/listing-keys/

use the prefix to find the key we want first. this may incur a performance penalty, but would reduce downtime to effectively nothing if properly implemented.

from kv-asset-handler.

So I just tested to see if this happens and I'm not seeing it happen anymore for some reason... KV seems to be updating perfectly. @fernandogrd I saw that you had put a 👍 on this issue, have you run into this recently?

from kv-asset-handler.

@EverlastingBugstopper I was waiting for this to be fixed so I could use the static website feature, it was a blocker for me.

from kv-asset-handler.