Scripts Documentation¶

Quick start scripts for the Microsoft Fabric Casino/Gaming POC. All scripts are provided in both PowerShell (Windows) and Bash (Linux/macOS) versions.

Quick Start¶

# Windows (PowerShell)
.\scripts\setup.ps1                    # Set up environment
.\scripts\generate-data.ps1 --quick    # Generate demo data
.\scripts\validate-environment.ps1     # Validate setup

# Linux/macOS (Bash)
./scripts/setup.sh                     # Set up environment
./scripts/generate-data.sh --quick     # Generate demo data
./scripts/validate-environment.sh      # Validate setup

Scripts Overview¶

setup.ps1 / setup.sh¶

Purpose: Complete environment setup for the POC.

What It Does¶

1. Checks prerequisites (Python 3.10+, Azure CLI, Bicep, Git)
2. Creates Python virtual environment (.venv)
3. Installs dependencies from requirements.txt
4. Validates Azure CLI login
5. Creates .env from .env.sample (if needed)
6. Displays next steps

Usage¶

# Windows
.\scripts\setup.ps1
.\scripts\setup.ps1 -SkipAzureLogin
.\scripts\setup.ps1 -VenvPath "C:\envs\fabric-poc"

# Linux/macOS
./scripts/setup.sh
./scripts/setup.sh --skip-azure-login
./scripts/setup.sh --venv-path /path/to/venv

Parameters¶

Prerequisites¶

• Python 3.10 or later
• Git
• Azure CLI (for deployment)
• Bicep CLI (installed automatically via Azure CLI)

generate-data.ps1 / generate-data.sh¶

Purpose: Generate synthetic casino/gaming data for the POC.

What It Does¶

1. Generates data across all casino domains
2. Supports multiple output formats (Parquet, JSON, CSV)
3. Configurable data volumes
4. Provides progress and summary statistics

Usage¶

# Windows - Quick demo mode
.\scripts\generate-data.ps1 --quick

# Full generation
.\scripts\generate-data.ps1 --all --days 30

# Specific data types
.\scripts\generate-data.ps1 -Slots -SlotCount 100000 -Players -PlayerCount 5000

# Custom output
.\scripts\generate-data.ps1 --all -OutputDir "D:\data" -Format json

# Linux/macOS - Quick demo mode
./scripts/generate-data.sh --quick

# Full generation
./scripts/generate-data.sh --all --days 30

# Specific data types
./scripts/generate-data.sh --slots --slot-count 100000 --players --player-count 5000

# Custom output
./scripts/generate-data.sh --all --output-dir /data/output --format json

Parameters¶

Data Type Flags¶

Quick Mode Volumes¶

When using --quick, the following reduced volumes are used:

deploy-infrastructure.ps1 / deploy-infrastructure.sh¶

Purpose: Deploy Azure infrastructure using Bicep templates.

What It Does¶

1. Loads configuration from .env file
2. Validates required variables
3. Creates Azure resource group
4. Deploys Bicep templates
5. Saves deployment outputs to deployment-outputs.json

Usage¶

# Windows
.\scripts\deploy-infrastructure.ps1
.\scripts\deploy-infrastructure.ps1 -Environment staging
.\scripts\deploy-infrastructure.ps1 -WhatIf
.\scripts\deploy-infrastructure.ps1 -NoPrompt

# Linux/macOS
./scripts/deploy-infrastructure.sh
./scripts/deploy-infrastructure.sh --environment staging
./scripts/deploy-infrastructure.sh --what-if
./scripts/deploy-infrastructure.sh --no-prompt

Parameters¶

Required .env Variables¶

AZURE_SUBSCRIPTION_ID=<your-subscription-id>
PROJECT_PREFIX=fabricpoc
FABRIC_ADMIN_EMAIL=admin@domain.com

Optional .env Variables¶

AZURE_LOCATION=eastus2
FABRIC_CAPACITY_SKU=F64
ENABLE_PRIVATE_ENDPOINTS=false
LOG_RETENTION_DAYS=30

Deployment Outputs¶

After deployment, deployment-outputs.json contains:

{
    "deploymentName": "fabric-poc-dev-20250121-123456",
    "resourceGroup": "fabricpoc-dev-rg",
    "environment": "dev",
    "location": "eastus2",
    "timestamp": "2025-01-21T12:34:56Z",
    "outputs": {
        "storageAccountName": "fabricpocdevstorage",
        "fabricCapacityId": "/subscriptions/.../fabricCapacities/...",
        "logAnalyticsWorkspaceId": "..."
    }
}

validate-environment.ps1 / validate-environment.sh¶

Purpose: Comprehensive validation of environment setup.

What It Does¶

1. Checks all prerequisites
2. Validates configuration files
3. Tests Azure connectivity
4. Verifies Python dependencies
5. Tests generator imports
6. Runs smoke test (data generation)
7. Reports status with visual indicators

Usage¶

# Windows
.\scripts\validate-environment.ps1
.\scripts\validate-environment.ps1 -Quick

# Linux/macOS
./scripts/validate-environment.sh
./scripts/validate-environment.sh --quick

Parameters¶

Checks Performed¶

Prerequisites: - Python 3.10+ - Virtual environment - Git - Azure CLI - Bicep

Configuration: - .env file exists and configured - requirements.txt exists - Bicep templates exist - Data generator exists

Azure: - Azure CLI login status - Subscription access

Python: - Required packages importable - Generator classes importable - Data generation smoke test

Exit Codes¶

cleanup.ps1 / cleanup.sh¶

Purpose: Cleanup and teardown POC resources.

What It Does¶

1. Deletes Azure resource group (with confirmation)
2. Cleans local generated data
3. Removes Python virtual environment
4. Cleans cache directories

Usage¶

# Windows
.\scripts\cleanup.ps1 -DeleteData
.\scripts\cleanup.ps1 -DeleteAzure
.\scripts\cleanup.ps1 -DeleteVenv
.\scripts\cleanup.ps1 -All
.\scripts\cleanup.ps1 -All -Force
.\scripts\cleanup.ps1 -DeleteAzure -Environment staging

# Linux/macOS
./scripts/cleanup.sh --delete-data
./scripts/cleanup.sh --delete-azure
./scripts/cleanup.sh --delete-venv
./scripts/cleanup.sh --all
./scripts/cleanup.sh --all --force
./scripts/cleanup.sh --delete-azure --environment staging

Parameters¶

Safety Features¶

• Confirmation prompts: All destructive actions require confirmation
• Azure deletion: Requires typing the resource group name
• Force mode: Bypasses all prompts (use with caution)
• Selective cleanup: Delete only what you need

Typical Workflows¶

Initial Setup¶

# 1. Setup environment
.\scripts\setup.ps1

# 2. Validate setup
.\scripts\validate-environment.ps1

# 3. Generate test data
.\scripts\generate-data.ps1 --quick

Full POC Deployment¶

# 1. Setup environment
.\scripts\setup.ps1

# 2. Configure .env file
code .env

# 3. Generate full dataset
.\scripts\generate-data.ps1 --all --days 30

# 4. Deploy infrastructure
.\scripts\deploy-infrastructure.ps1

# 5. Validate everything
.\scripts\validate-environment.ps1

Cleanup After POC¶

# Delete everything
.\scripts\cleanup.ps1 -All

# Or selectively
.\scripts\cleanup.ps1 -DeleteData
.\scripts\cleanup.ps1 -DeleteAzure

Re-deploy to Different Environment¶

# Deploy to staging
.\scripts\deploy-infrastructure.ps1 -Environment staging

# Later, cleanup staging
.\scripts\cleanup.ps1 -DeleteAzure -Environment staging

Troubleshooting¶

"Python not found"¶

1. Install Python 3.10+ from https://www.python.org/downloads/
2. Ensure Python is in your PATH
3. Run setup.ps1 / setup.sh to create virtual environment

"Azure CLI not logged in"¶

az login
az account set --subscription <subscription-id>

"Bicep not installed"¶

az bicep install

"Module import failed"¶

1. Ensure virtual environment is activated
2. Run pip install -r requirements.txt
3. Check for conflicting package versions

"Deployment failed"¶

1. Check .env configuration
2. Verify Azure subscription access
3. Run with --what-if to preview changes
4. Check Azure Portal for detailed error messages

"Permission denied" (Linux/macOS)¶

chmod +x scripts/*.sh

Environment Variables Reference¶

The scripts use these environment variables from .env:

Cross-Platform Considerations¶

Line Endings¶

If you encounter issues running bash scripts on Windows or vice versa:

# Convert to Unix line endings
dos2unix scripts/*.sh

# Convert to Windows line endings
unix2dos scripts/*.ps1

Execution Policy (Windows)¶

If PowerShell scripts are blocked:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Permissions (Linux/macOS)¶

Make scripts executable:

chmod +x scripts/*.sh

Contributing¶

When modifying scripts:

1. Update both .ps1 and .sh versions
2. Test on all target platforms
3. Update this README with any new parameters
4. Follow existing code style and patterns