How amanzeht/simba-demo-api works
Project Simba demonstrates a PR-gated promotion pipeline alongside a small Express API. The API serves environment-specific status, health, and version responses; the documented promotion flow builds once for dev and reuses that image digest through test, UAT, and prod. Workflow and AWS wiring are represented only as documented; their source was not sampled.
Main entry points: deploy.yml GitHub Actions · index.js Express API · ecs-task-definition.json ECS services · Dockerfile Container image
Components 12
Demo API
- Express API
src/index.js - Catalog response
src/index.js - Health route
src/index.js - Version route
src/index.js
Promotion pipeline
- GitHub Actions
.github/workflows/deploy.yml - Container image
Dockerfile
AWS environments
- Image registry
- ECS services
ecs-task-definition.json - Dev / test / UAT / prod
Other components
- Engineer
- Promotion PR
- API visitor
Connections 12
- Engineer → Promotion PR: opens PR
- Promotion PR → GitHub Actions: triggers checks
- GitHub Actions → Container image: builds on dev
- GitHub Actions → Image registry: pushes image
- GitHub Actions → Image registry: retags digest
- GitHub Actions → ECS services: updates service
- ECS services → Dev / test / UAT / prod: runs tasks
- API visitor → Dev / test / UAT / prod: requests URL
- Dev / test / UAT / prod → Express API: routes request
- Express API → Catalog response: serves root
- Express API → Health route: serves health
- Express API → Version route: serves version