While doing a release, it seems the dataset that's getting released is broken (getting 404)

[corneliusroemer]

I've noticed that while the release is ongoing for SARS-CoV-2, the new dataset is selectable, but when you click on it you get a 404 due to README and CHANGELOG not being available.

This seems to be only happening while the release action is running.

[corneliusroemer]

Now things work again - so it seems to be an issue for a short time only - probably not worth investing much time to fix if it's not super easy

[ivan-aksamentov]

Yep, there might be a few seconds between new index.json is already copied to S3 and the rest of the files are still being copied plus then their Cloudfront cache invalidation completes.

index.json is not cached currently to avoid being stale (here it functions similarly to how index.html is for web apps)

There is probably a smarter way to do atomic, zero-downtime deployments. One improvement could be to reorder the copies - copy data files first, invalidate cache and then copy index.json when data it points to is in place.