Issue #4 added Lambda support to the hubverse_transform Python package.
Those changes added a way to package and deploy hubverse_transform to the hubverse-transform-model-output Lambda on the Hubverse's AWS account.
However, the deployment is manual (i.e., if the hubverse_transform code changes, someone will need to manually run the deployment script and push those code changes to AWS).
This issue represents the next step: packaging and deploying the Lambda-related code via a GitHub action that runs when changes are merged to the repo's main branch.
Definition of done
[ ] Create a new GitHub action that performs the same steps as the current deploy script (deploy_lambda.sh)'
[ ] The new action runs whenever files in the src/ or faas/ directory are updated, and the changes merged to this repo's main branch
Background
Issue #4 added Lambda support to the
hubverse_transformPython package.Those changes added a way to package and deploy
hubverse_transformto thehubverse-transform-model-outputLambda on the Hubverse's AWS account.However, the deployment is manual (i.e., if the
hubverse_transformcode changes, someone will need to manually run the deployment script and push those code changes to AWS).Prerequisite: Infectious-Disease-Modeling-Hubs/hubverse-infrastructure#39
Work required
This issue represents the next step: packaging and deploying the Lambda-related code via a GitHub action that runs when changes are merged to the repo's
mainbranch.Definition of done
deploy_lambda.sh)'src/orfaas/directory are updated, and the changes merged to this repo'smainbranch