Skip to content

feat: Infra restructure#2272

Draft
AjitPadhi1-Microsoft wants to merge 12 commits into
Azure-Samples:dev-v2from
AjitPadhi1-Microsoft:infra-restructure
Draft

feat: Infra restructure#2272
AjitPadhi1-Microsoft wants to merge 12 commits into
Azure-Samples:dev-v2from
AjitPadhi1-Microsoft:infra-restructure

Conversation

@AjitPadhi1-Microsoft

Copy link
Copy Markdown

Purpose

  • ...

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

AjitPadhi1-Microsoft and others added 12 commits June 23, 2026 16:53
… Apps

Author v2/infra/bicep/main.bicep so the 'bicep' flavor is functionally equivalent to v2/infra/avm/main.bicep while using the granular native-resource modules under v2/infra/bicep/modules/*. Frontend and backend run on Azure Container Apps; the Functions host runs as a code/zip Linux Function App.

- Enable the bicepDeployment module in the v2/infra/main.bicep router and route via DEPLOYMENT_FLAVOR (now defaulted to bicep in main.parameters.json).
- Mirror the avm resource graph, env vars, model deployments and outputs (43 app outputs identical; VNet/Bastion outputs omitted as the Docker flavor has no private-networking layer).
- Author all RBAC natively in main.bicep (avm uses a role-assignment module) using deterministic existing-resource refs plus explicit dependsOn, since module files are frozen.
- Declare the 6 ingestion storage queues natively (doc-processing/blob-events/add-url + poison).
- Documented forced deviations from avm: Log Analytics always deployed and storage allowSharedKeyAccess=true (required by the unchanged container-app-environment and function-app modules); Event Grid uses first-party StorageQueue delivery.
- No module files changed. Both v2/infra/main.bicep and v2/infra/bicep/main.bicep build clean (az bicep build, exit 0, no warnings).
The conditional router outputs in v2/infra/main.bicep referenced avmDeployment in both the true and false ternary branches, so in 'bicep' flavor the outputs pointed at the undeployed avm module and ARM rejected the template (InvalidTemplate: output reference to module.avm requires an API version). Point the false (isBicep) branch at bicepDeployment so each flavor reads outputs from the module it actually deploys, mirroring the working avm path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants