Skip to main content

Azure Deployment

info

AquaGen API runs on Azure App Service (prod-aquagen). Deployment is done directly from VS Code using the Azure App Service extension — no CI/CD pipeline.

Deployment Workflow​

code changes → push to production branch → deploy to prod-aquagen via VS Code Azure extension
  1. Make and test changes locally
  2. Push to the production branch: 
    git checkout production
    git pull origin production
    git merge feature/your-branch
    git push origin production
  3. Open VS Code → Azure extension → App Services → right-click prod-aquagen → Deploy to Web App
  4. Select the workspace folder when prompted
  5. VS Code zips the workspace, uploads, and builds on Azure — takes ~20 seconds

The terminal output confirms:

✓ Zip and deploy workspace  ~14s
✓ Build app "prod-aquagen" in Azure  ~6s
✓ Deploy to app "prod-aquagen"  Succeeded in 21s

Azure App Services​

The following App Service instances are running under the Microsoft Azure Sponsorship subscription:

App ServicePurpose
prod-aquagenProduction API

Azure Resources​

ResourceService
Cosmos DBPrimary database (standard-categories and test databases)
Azure Key VaultAll secrets and credentials
Application InsightsMonitoring and telemetry
Azure ADAdmin SSO authentication

All secrets are fetched from Key Vault at startup via smi.get(SecretName.XYZ). No credentials are stored in the codebase or app settings directly.

Troubleshooting​

Deployment failed

Check the VS Code Azure output panel for the error message.

App not starting after deploy

Stream logs from the Azure extension: Azure → App Services → prod-aquagen → Logs (Read-only)

Common causes
  • Missing or changed Key Vault secret name
  • Dependency not in requirements.txt
  • Python version mismatch

Next Steps​