Montagu System

The Montagu Monorepo

Directories

• api/ - Montagu API. Previously at vimc/montagu-api
• db/ - the database. Previously at vimc/montagu-db
• deploy/ - the deploy tool. Previously at vimc/montagu-deploy and on PyPi
• proxy/ - the proxy. Previously at vimc/montagu-proxy
• task-queue - the task queue, primarily used to run diagnostic report through Packit on burden estimate upload through the API. Previously at vimc/monbagu-task-queue
• webapps - the web portals, for Admin and Modellers' contributions. Previously at vimc/montag-webapps

Still to do

We need to rationalise e2e tests which are reproduced in several component directories. These tests can be brittle and some are currently being skipped and should be reinstated when we put in one set of e2e tests for everything. The problematic tests are those which require all component containers to run. Typically these are scenarios where Montagu API needs to communicate with Packit - to start a task via the task queue, or to create a new user. These require all containers because Packit Auth needs to go through the proxy, and because the proxy requires the web apps to be running..

Tests which are currently skipped or commented out:

• api/src/app/test/kotlin/org/vaccineimpact/api/test/clients/CeleryClientTests.kt "can call task" l.52-53