fix: merging dev changes to main branch

[Roopan-Microsoft]

Purpose

• This pull request updates deployment documentation and infrastructure configuration to improve clarity, streamline setup, and enhance parameterization for Azure resources. The most significant changes include updating documentation for environment file setup, frontend build steps, and infrastructure outputs, as well as parameterizing the Azure OpenAI API version.

Documentation improvements:

• Updated both DeploymentGuide.md and LocalDeployment.md to clarify that the .env file should be created in the src/backend directory, and added instructions for automatically generating this file when using azd. Also, emphasized setting APP_ENV to "dev" and provided clearer guidance on populating environment variables. [1] [2]
• Added a required step to build the frontend (npm install and npm run build in src/frontend) before running the application, ensuring necessary assets are generated. [1] [2]
• Updated references in documentation from macae-dev.bicep to the new infra/main.bicep deployment file, and clarified related instructions and role assignments. [1] [2] [3]

Infrastructure and parameterization:

• Introduced a new azureopenaiVersion parameter in infra/main.bicep (default: '2025-01-01-preview'), and updated the container app module to use this parameter, improving flexibility for API versioning. [1] [2]
• Added multiple outputs to infra/main.bicep for key resource connection strings, endpoints, and deployment names, making it easier to configure the application and automate environment variable setup.

Parameter documentation:

• Changed default values for AZURE_LOCATION and AZURE_ENV_OPENAI_LOCATION in CustomizingAzdParameters.md from hardcoded regions to user-selected values during deployment, clarifying that these are now interactive inputs.

General terminology updates:

• Updated solution naming in documentation from "Chat With Your Data accelerator" to "Multi-Agent solutions accelerator" or "Multi Agent Solution accelerator" for consistency with the current project scope. [1] [2]

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

[github-actions]

🎉 This PR is included in version 2.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀