setupInfra

Prompt file imported from aiappsgbb/VIPER (.github/prompts/setupInfra.prompt.md). Fill in {{planFile}}, {{collectionFile}}, {{collector}}, {{initialPrompt}}, {{researchPlan}} before use. Copyright stays with the author.

Configure the main.bicep file to set up a comprehensive Azure infrastructure using all available modules in the infra/core directory.

Critical: Follow Bicep Deployment Best Practices for all infrastructure components.

Research Context (Optional - If Available)

If research planning and collection templates were completed prior to this task, reference them here for implementation guidance:

Plan File Used: {{planFile}} Collection File Used: {{collectionFile}} Date: [YYYY-MM-DD] Collector: {{collector}} Initial Prompt (verbatim): {{initialPrompt}} Referenced Research Plan: {{researchPlan}}

Research Artifacts Location:

• Plan: .github/scratchpad/research-plan-[TIMESTAMP].md (if exists)
• Collection: .github/scratchpad/research-collection-[TIMESTAMP].md (if exists)

Implementation Notes:

• Review research collection findings for Azure infrastructure patterns, Bicep configurations, and service dependencies
• Use consolidated environment variables from collection template
• Reference code snippets from findings for infrastructure implementation
• Validate against research gaps identified in collection phase

1. Update the main.bicep file to include all modern Azure services:

2. Uncomment and configure the following modules with proper dependencies:

   • User Assigned Managed Identity (foundational security)
   • Key Vault (secure secret management)
   • Storage Account (general purpose storage)
   • Log Analytics Workspace & Application Insights (monitoring)
   • Container Registry (container image storage)
   • Container Apps Environment (container hosting platform)
   • Container App (application deployment)
   • AI Search (intelligent search capabilities)
   • Cosmos DB (NoSQL database)
   • AI Foundry (AI development platform)

3. Set up proper dependencies between modules:

   • Managed Identity should be created first
   • Monitoring (Log Analytics) before Container Apps Environment
   • Key Vault and Storage Account before AI Foundry
   • Container Registry before Container Apps

4. Configure role assignments:

   • Grant Container App managed identity access to Container Registry
   • Grant managed identity Key Vault access
   • Grant AI services access to Storage and Key Vault

5. Add comprehensive outputs including:

   • All resource IDs and names
   • Connection strings (where appropriate)
   • Service endpoints
   • Resource group information

6. Include proper parameter validation and descriptions

7. Use the resource naming convention with abbreviations and resource tokens

8. Ensure all modules use consistent tagging

9. Add comments explaining the purpose of each module and dependencies

The infrastructure should be production-ready with proper security, monitoring, and resource organization.