cleanup v3
Closed this issue · 9 comments
With #401, we migrated to V4 data spec and v3 is not needed.
- remove all references to v3 in the covid repo
- remove all references to v3 in the epimodel repo (https://github.com/epidemics/epimodel/blob/c909fd0b849fa33e1133ac0ab9e7ed7a2a0f0af7/config.yaml#L22)
- delete old data from GCS to save space
I think we can do this now
#437 fixes this for the frontend
@mathijshenquet Can I delete the old files from GCS? Or do we need a full pipeline run first? :-)
The v3 files can be deleted. In fact everything not referenced by a data-*-v4.json. Be careful though as I don't know how to regenerate the Balochistan stuff.
Skimming through the loaded resources, I see there is still v3 loaded on the main page:
.
Other than that, it seems that the latest generated file is from April 17.
Balochistan is probably: gs://static-covid/static/data-balochistan-v4.json and that ones uses 2020-05-04T02:50:54.174593+00:00. @lagerros can you confirm please that this is the correct balochistan file?
I cannot reproduce loading data-main-v3.json. Is this on epidemicforecasting.org/?
(dealt with via slack)
This has been fixed by 6f31e7c
I deleted what was possible, we are on only 350MB in the bucket, so negligible 👍 .