the metadata updates invoked the "new model-output file" lambda, which re-processed all 1128 files and wrote updated output to bsweger-flusight-forecast/model-output
➜ python faas/lambda_retrigger_model_output_add.py bsweger-flusight-forecast
Updating metadata for all files in bsweger-flusight-forecast/raw/model-output/
Processing raw/model-output/CADPH-FluCAT_Ensemble/2023-10-14-CADPH-FluCAT_Ensemble.csv
Processing raw/model-output/CADPH-FluCAT_Ensemble/2023-10-21-CADPH-FluCAT_Ensemble.csv
Processing raw/model-output/CADPH-FluCAT_Ensemble/2023-10-28-CADPH-FluCAT_Ensemble.csv
[snip]
Updated metadata for 1129 files in bsweger-flusight-forecast/raw/model-output/
Resolves #27
First iteration of a way to re-trigger the lambda function that fires when new data is added to the raw/model-output/ folder of a hub's S3 bucket.
To try this as part of code review:
python faas/lambda_retrigger_model_output_add.py bsweger-flusight-forecast
I ran this against the
bsweger-flusight-forecast
test hub and confirmed that:x-amz-meta-manual-update
metadata field was added to all files inbsweger-flusight-forecast/raw/model-output
:bsweger-flusight-forecast/model-output