🏗️ infra: implement Phase 0.1 Azure Infrastructure with Bicep AVMs #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Complete implementation of Azure infrastructure using Bicep with Azure Verified Modules (AVMs) as specified in the Luminous roadmap Phase 0.1. Infrastructure modules created: - Cosmos DB with 11 containers for multi-tenant data - App Service and App Service Plan for .NET 10 API - Function Apps for sync and import processing - Static Web App for Angular web application - Redis Cache for session management - SignalR Service for real-time sync - Service Bus with queues for async messaging - Key Vault for secrets management - App Configuration for centralized config - Storage Account for blob storage - Log Analytics and Application Insights for monitoring Additional deliverables: - Environment parameter files (dev, staging, prod) - Deployment scripts (Bash and PowerShell) - Azure Infrastructure documentation ROADMAP.md updated to reflect Phase 0.1 completion.
Refactored infrastructure to use Azure Verified Modules (AVMs) directly from the public Bicep registry (br/public:avm/res/...) instead of recreating them as local modules. Changes: - Updated main.bicep to reference 13 AVMs from registry: - br/public:avm/res/resources/resource-group:0.4.0 - br/public:avm/res/operational-insights/workspace:0.9.0 - br/public:avm/res/insights/component:0.4.1 - br/public:avm/res/key-vault/vault:0.9.0 - br/public:avm/res/app-configuration/configuration-store:0.5.1 - br/public:avm/res/document-db/database-account:0.8.1 - br/public:avm/res/storage/storage-account:0.14.3 - br/public:avm/res/cache/redis:0.8.0 - br/public:avm/res/service-bus/namespace:0.10.0 - br/public:avm/res/signal-r-service/signal-r:0.5.0 - br/public:avm/res/web/serverfarm:0.3.0 - br/public:avm/res/web/site:0.11.1 - br/public:avm/res/web/static-site:0.6.0 - Removed 13 local module files (no longer needed) - Updated parameter files to match AVM parameter names - Updated AZURE-INFRASTRUCTURE.md with AVM reference table - Updated ROADMAP.md with implementation details Benefits of using AVMs directly: - Pre-validated security and compliance patterns - Maintained by Microsoft and community - Semantic versioning for predictable upgrades - Less code to maintain
trickpatty
approved these changes
Dec 21, 2025
trickpatty
added a commit
that referenced
this pull request
Dec 24, 2025
trickpatty
added a commit
that referenced
this pull request
Dec 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Complete implementation of Azure infrastructure using Bicep with Azure
Verified Modules (AVMs) as specified in the Luminous roadmap Phase 0.1.
Infrastructure modules created:
Additional deliverables:
ROADMAP.md updated to reflect Phase 0.1 completion.