The MWDP project originated the infra template. Since then, a lot of progress has happened on the infra template, but this project's infra has stayed static.
In this previous tech spec, we outlined what it would look like to migrate to the infra template. This tech spec asks a slightly different question. I would like to know what it would take to re-implement the infra for the eligibility screener (in other words, starting over) using v0.2.0 release of the infra template. Imagine we could destroy the current AWS account and start fresh.
Tasks
Create a tech spec that:
Outlines what AWS resources are needed to deploy the eligibility screener (e.g. ECR, ECS, IAM, etc)
Outlines the new CI/CD process and any changes that need to be made to the github repo
Explains pros/cons of re-implementing
Outlines risks for re-implementing
Estimates the amount of effort to re-implement
Outlines the plan for re-implementing
Outlines the plan for testing the implementation (can be very simple!)
Notes: This tech spec can and should re-use content from the previous tech spec where relevant.
This ticket is part of the tech spec that came out of #196. The other ticket proposals can be read here
Context: This ticket involves migrating network configuration from the infra-template to the eligibility screener. While not much work is needed, these configurations span quite a few files.
Work involved:
Make sure the networking resources are configured in a way that matches the infra-template
Networking.tf (screener) is fairly close to what we should see in
Make sure the networks module is copied over and called appropriately.
Definition of Done: Terraform can plan and apply successfully, screener has no change in functionality.
This ticket is part of the tech spec that came out of #196. The other ticket proposals can be read here
Context: This ticket involves migrating a module from the infra-template to the eligibility screener, however it will require maneuvering a few resources, and making sure that the module references correct information(e.g. AWS account, dynamo DB table) Definition of Done: Terraform can plan and apply successfully, screener has no change in functionality.