fix: merging dev to main

[Roopan-Microsoft]

Purpose

• This pull request introduces several improvements to the Azure deployment configuration and infrastructure code, focusing on enabling local debugging, clarifying deployment workflows, and ensuring correct resource permissions. The most significant changes add deployer-specific role assignments for easier local development, update resource references for reliability, and improve documentation for custom deployments.

Infrastructure enhancements for local debugging and permissions:

• Added deployer (local user/service principal) role assignments to storageAccount, cosmosDb, and AI resources, granting necessary permissions for local debugging and development. (infra/main.bicep) [1] [2] [3] [4] [5] [6] [7]
• Introduced new output variables to log deployer information for debugging purposes. (infra/main.bicep)
• Added a new reusable module for role assignments to Cognitive Services accounts, supporting multiple role types. (infra/modules/role.bicep)

Resource reference and dependency fixes:

• Corrected variable usage for AI resource names and added explicit dependencies to ensure reliable deployment order. (infra/main.bicep) [1] [2] [3]
• Improved subnet reference handling for container apps to prevent deployment errors. (infra/main.bicep)

Documentation and workflow improvements:

• Updated the deployment guide to clarify steps for deploying local changes, including file renaming instructions for custom deployments. (docs/DeploymentGuide.md)
• Added a developer-focused Azure Developer CLI configuration file, defining services and deployment hooks for easier local development and endpoint discovery. (azure_custom.yaml)

Parameter and code quality improvements:

• Added comments and annotations to clarify parameter usage and suppress unused parameter warnings. (infra/main.bicep)
• Improved code readability by extracting deployer information into variables. (infra/main.bicep)

These changes collectively streamline the deployment process, improve support for local development and debugging, and ensure that resource permissions and references are correctly managed.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀