How microsoft/azuretre works
Project type and purpose
• This is a full-stack, cloud-native accelerator (Azure TRE) combining infrastructure-as-code (Terraform), microservices (API, functions, processors), client applications (web UI, CLI), and DevOps pipelines. Its goal is to enable self-service provisioning of secure research workspaces on Azure, with extensible “shared services,” workspace templates, airlock import/export, cost reporting, and AAD integration.
File structure
• Top-level components:
• core/terraform & templates/…: Terraform modules for core resources, shared services, workspace services, workspace templates
• api_app: Python FastAPI-based REST API, DB repositories, Pydantic schemas, service bus and event grid integrations, tests
• airlock_processor: Azure Functions triggered by Blob, Queue, and Service Bus events for airlock import/export
• resource_processor: VMSS Porter Runner service handling Service Bus messages to provision resources
• cli: Python-based command-line interface that wraps API calls
• ui: React + TypeScript single-page app (Vite) calling the API
• devops & .github: CI/CD pipelines, GitHub Actions, DevOps/Terraform bootstrap scripts
• e2e_tests: pytest-based end-to-end tests against deployed endpoints
• docs: Architecture, usage guides, templates documentation