This directory contains the Bicep template and a deployment script for provisioning Azure services in LocalStack for Azure. For further details about the sample application, refer to the Azure Web App with Azure CosmosDB for MongoDB.
Before deploying this solution, ensure you have the following tools installed:
- LocalStack for Azure: Local Azure cloud emulator for development and testing
- Visual Studio Code: Code editor installed on one of the supported platforms
- Bicep extension: VS Code extension for Bicep language support and IntelliSense
- Docker: Container runtime required for LocalStack
- Azure CLI: Azure command-line interface
- Azlocal CLI: LocalStack Azure CLI wrapper
- Python: Python runtime (version 3.12 or above)
- jq: JSON processor for scripting and parsing command outputs
The deploy.sh Bash script uses the azlocal CLI instead of the standard Azure CLI to work with LocalStack. Install it using:
pip install azlocalFor more information, see Get started with the az tool on LocalStack.
The deploy.sh script creates the Azure Resource Group for all the Azure resources, while the main.bicep Bicep module creates the following Azure resources:
- Azure CosmosDB Account (MongoDB API): A globally distributed database account configured for MongoDB workloads, with multi-region failover.
- MongoDB Database: The
sampledbdatabase for storing application data. - MongoDB Collection: The
activitiescollection withinsampledbfor storing vacation activity records. - Azure App Service Plan: The compute resource that hosts the web application.
- Azure Web App: Hosts the Python Flask single-page application (Vacation Planner), connected to CosmosDB for MongoDB.
- App Service Source Control: (Optional) Configures automatic deployment from a public GitHub repository.
The web app allows users to plan and manage vacation activities, storing all activity data in a MongoDB collection.
Before deploying the main.bicep template, update the bicep.bicepparam file with your specific values:
using 'main.bicep'
param prefix = 'local'
param suffix = 'test'
param runtimeName = 'python'
param runtimeVersion = '3.13'
param databaseName = 'sampledb'
param collectionName = 'activities'
param username = 'paolo'
param primaryRegion = 'westeurope'
param secondaryRegion = 'northeurope'See deploy.sh for the complete deployment automation. The script performs:
- Detects environment (LocalStack vs Azure Cloud) and uses appropriate CLI
- Creates resource group if it doesn't exist
- Optionally validates the Bicep template
- Optionally runs what-if deployment for preview
- Deploys the main.bicep template with parameters from main.bicepparam
- Extracts deployment outputs (Web App name, CosmosDB details)
- Creates zip package of the Python application
- Deploys the zip to Azure Web App
You can set up the Azure emulator by utilizing LocalStack for Azure Docker image. Before starting, ensure you have a valid LOCALSTACK_AUTH_TOKEN to access the Azure emulator. Refer to the Auth Token guide to obtain your Auth Token and specify it in the LOCALSTACK_AUTH_TOKEN environment variable. The Azure Docker image is available on the LocalStack Docker Hub. To pull the Azure Docker image, execute the following command:
docker pull localstack/localstack-azure-alphaStart the LocalStack Azure emulator using the localstack CLI, execute the following command:
export LOCALSTACK_AUTH_TOKEN=<your_auth_token>
IMAGE_NAME=localstack/localstack-azure-alpha localstack startNavigate to the bicep folder:
cd samples/web-app-cosmosdb-mongodb-api/python/bicepMake the script executable:
chmod +x deploy.shRun the deployment script:
./deploy.shAfter deployment, you can use the validate.sh script to verify that all resources were created and configured correctly:
#!/bin/bash
# Variables
ENVIRONMENT=$(az account show --query environmentName --output tsv)
# Choose the appropriate CLI based on the environment
if [[ $ENVIRONMENT == "LocalStack" ]]; then
echo "Using azlocal for LocalStack emulator environment."
AZ="azlocal"
else
echo "Using standard az for AzureCloud environment."
AZ="az"
fi
# Check resource group
$AZ group show \
--name local-rg \
--output table
# List resources
$AZ resource list \
--resource-group local-rg \
--output table
# Check Azure Web App
$AZ webapp show \
--name local-webapp-test \
--resource-group local-rg \
--output table
# Check Azure CosmosDB account
$AZ cosmosdb show \
--name local-mongodb-test \
--resource-group local-rg \
--output table
# Check MongoDB database
$AZ cosmosdb mongodb database show \
--name sampledb \
--account-name local-mongodb-test \
--resource-group local-rg \
--output table
# Check MongoDB collection
$AZ cosmosdb mongodb collection show \
--name activities \
--database-name sampledb \
--account-name local-mongodb-test \
--resource-group local-rg \
--output tableTo destroy all created resources:
# Delete resource group and all contained resources
az group delete --name local-rg --yes --no-wait
# Verify deletion
az group list --output tableThis will remove all Azure resources created by the CLI deployment script.