How slayersarthak/dockerized-pythonapi-with-cicd works
This repository demonstrates a Flask API delivered through a container-based CI/CD workflow. The user-facing path is a request to the API’s health endpoint; the delivery path starts with a code change, builds and exercises the API alongside PostgreSQL, then publishes and deploys an image to Cloud Run. The README also describes Artifact Registry and Cloud Build. Those deployment services are documented capabilities, but their implementation is not visible in the sampled source, and the README is inconsistent about whether CD is automated.
Main entry points: ci.yml GitHub Actions · docker-compose.yml Compose stack · Dockerfile Container image · test_app.py Integration tests
Components 13
API service
- Flask API
app.py - Health endpoint
app.py
Local stack
- Container image
Dockerfile - Compose stack
docker-compose.yml - PostgreSQL
docker-compose.yml
Continuous integration
- GitHub Actions
.github/workflows/ci.yml - Integration tests
test_app.py
Cloud deployment
- Artifact Registry
- Cloud Build
- Cloud Run
- Live HTTPS service
Other components
- API caller
- Code change
Connections 12
- API caller → Health endpoint: requests
README.md - Code change → GitHub Actions: triggers
README.md - GitHub Actions → Container image: builds
README.md - GitHub Actions → Compose stack: starts
README.md - Compose stack → Flask API: runs
README.md - Compose stack → PostgreSQL: starts
README.md - GitHub Actions → Integration tests: runs
README.md - Integration tests → Health endpoint: checks
README.md - Container image → Artifact Registry: stores
README.md - Cloud Build → Container image: builds
- Artifact Registry → Cloud Run: supplies image
README.md - Cloud Run → Live HTTPS service: serves
README.md