It would be good to have a way to force existing "raw" model-output files in a cloud-enabled hub's S3 bucket to trigger the transform AWS lambda (the one that normally runs when new uploads to S3 occur).
A good example of a use case is being able to re-process the 2023-24 CDC FluSight model-output files now that we've deployed a hubverse-transform patch to fix the schema inconsistencies.
This is a "break glass in case of emergency" function for use on Hubverse-hosted hubs, so it doesn't need to be polished/user-facing (in fact, it won't work unless the user has write access to S3 buckets in the Hubverse AWS account).
Definition of done
[ ] Script that re-triggers the S3 update event for files in the raw/model-output directory of a hub's bucket
[ ] Above script accepts S3 bucket name as a parameter
Background
It would be good to have a way to force existing "raw" model-output files in a cloud-enabled hub's S3 bucket to trigger the transform AWS lambda (the one that normally runs when new uploads to S3 occur).
A good example of a use case is being able to re-process the 2023-24 CDC FluSight model-output files now that we've deployed a hubverse-transform patch to fix the schema inconsistencies.
This is a "break glass in case of emergency" function for use on Hubverse-hosted hubs, so it doesn't need to be polished/user-facing (in fact, it won't work unless the user has write access to S3 buckets in the Hubverse AWS account).
Definition of done
raw/model-outputdirectory of a hub's bucket