How woedem24/azure-llm-pipeline works
This is an event-driven Azure document-analysis pipeline: a text-file upload triggers processing, GPT-4o produces structured analysis, Cosmos DB stores it, and an HTTP endpoint retrieves recent results. The sampled function source shows validation, retry classification, secret/client construction, and database operations. Terraform is documented as provisioning infrastructure, but its resource relationships were not sampled, so they are not mapped here.
Main entry points: function_app.py Client builders
Components 14
Ingestion & API
- Blob trigger handler
function_app.py - Document validation
function_app.py - Results HTTP endpoint
function_app.py
AI Analysis
- Document analysis
function_app.py
Cloud Integrations
- Input Blob Storage
- Client builders
function_app.py - Secret access
function_app.py - Azure Key Vault
- Azure OpenAI
Result Storage
- Result writer
function_app.py - Results query
function_app.py - Azure Cosmos DB
Other components
- File uploader
- Results consumer
Connections 16
- File uploader → Input Blob Storage: uploads file
README.md - Input Blob Storage → Blob trigger handler: triggers
function_app.py - Blob trigger handler → Document validation: reads and validates
function_app.py - Document validation → Document analysis: calls
function_app.py - Document analysis → Client builders: builds client via
function_app.py - Client builders → Secret access: fetches credentials via
function_app.py - Secret access → Azure Key Vault: reads secrets
function_app.py - Document analysis → Azure OpenAI: requests analysis
function_app.py - Blob trigger handler → Result writer: persists analysis via
function_app.py - Result writer → Client builders: gets container via
function_app.py - Result writer → Azure Cosmos DB: upserts result
function_app.py - Results consumer → Results HTTP endpoint: requests results
README.md - Results HTTP endpoint → Results query: queries via
function_app.py - Results query → Client builders: gets container via
function_app.py - Results query → Azure Cosmos DB: queries partition
function_app.py - Results HTTP endpoint → Results consumer: returns JSON
function_app.py